Repository navigation
Conversation
This branch has not been deployed
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.
Document how to run agenix from a project root or descendant directory using parent discovery of
agenix-rules.nix. Include a root bridge that prefixes keys from a nested rules file, plus an explicitAGENIX_RULESexample using Git to locate the project root.The guide states the filename base, nearest-file precedence, legacy-name behavior, and the absence of recursive descendant discovery so users can select the intended rules deterministically.
Validation: exercised the documented bridge with the real CLI, editing from the root and a nested directory, decrypting, rekeying one file, checking recipients, and selecting the nested rules explicitly. The documentation build passed. Based on #429.
Closes #201.
Related to #23: parent-directory rules discovery addresses one of the original CLI concerns while retaining Nix rules. Replacing the CLI language or configuration schema remains a separate maintainer decision.