Add option to crash autorestic
when key is missing instead of generating a new key
#383
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.
Relates to #202
This PR adds the
requireKey
field to the backend config.Normally, when
autorestic check
finds a backend without a key, it will generate a new key and update the config to add this key. This option prevents this behavior. WhenrequireKey: true
is set on a backend and no key is found,autorestic
will crash instead of generating a key and updating the config.This should help accidental problems from misconfiguration when managing
auotrestic
through configuration management tools.