Repository navigation
Conversation
Fixes getsops#1061 When a subcommand is mistyped (e.g. 'sops updateKeys' instead of 'updatekeys'), the argument is treated as a file path and the user only sees 'error loading config: no matching creation rules found', which suggests a config problem even though the config was parsed successfully. State that the config was parsed fine, include the file path, and hint that a mistyped subcommand is treated as a file path. Signed-off-by: NUAAwqy <146524024+NUAAwqy@users.noreply.github.com>
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
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.
Fixes #1061
When a subcommand is mistyped (e.g.
sops updateKeys some-file.yamlinstead ofupdatekeys), the argument is treated as a file path and the user only seeserror loading config: no matching creation rules found— which suggests a config problem even though the config was parsed successfully.The error now states that the config file was parsed successfully, includes the file path, and hints that a mistyped subcommand is treated as a file path (using the exact example from the issue).