Recreate token if store configuration changes #29
Conversation
This file contains 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
bastjan
force-pushed
the
recreate-token-if-config-change
branch
2 times, most recently
from
b824d03 to
c1b0db2
Compare
This re-encrypts the S3 store secrets if GPG keys change.
bastjan
force-pushed
the
recreate-token-if-config-change
branch
from
c1b0db2 to
f1ba99a
Compare
DebakelOrakel
approved these changes
Mar 28, 2024
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.
This re-encrypts the S3 store secrets if GPG keys change for example.
Also allows log store to log additional fields to make testing easier.
Checklist
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog