docs: add declarative manifest-plugins section to secrets management#45
Open
tanjadev wants to merge 1 commit into
Open
docs: add declarative manifest-plugins section to secrets management#45tanjadev wants to merge 1 commit into
tanjadev wants to merge 1 commit into
Conversation
Documents the upcoming [plugins] manifest section as an experimental, declarative alternative to hand-written on-activate retrieval hooks, using the in-development 1Password plugin as the example. Based on the Forge secrets-management effort (ADR-001 reference-only JIT, ADR-002 generic plugin system) and the manifest-plugins-prototype branch. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new "Declarative secrets with manifest plugins" section to the secrets-management concept page, describing the upcoming
[plugins]manifest section as a declarative alternative to hand-writtenon-activateretrieval hooks. Purely additive — the existing JIT/hook content is unchanged.Content is based on:
manifest-plugins-prototypebranch in the flox repo (activation ordering, dev/build-only modes, plugin-owned table shape)The section:
[plugins]not yet in a stable manifest schema; older Flox versions reject it with an "unknown field" error)flox/1passwordin[install], then[plugins.1password]mapping env var names toop://vault/item/fieldreferenceson-activate(hooks and services see the vars), dev/build modes only, primary auth stays with the storeNote
This page mints the canonical
[plugins.1password]TOML example — no literal example exists in the effort docs or prototype. Worth confirming theop://reference format (vs. bare paths) with the effort owner before the plugin ships.Test plan
mint broken-linkspasses🤖 Generated with Claude Code