feat(parameterstore): add support to set parameter tier for pushsecrets #3581
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
Signed-off-by: Victor Santos <vsantos.py@gmail.com>
|
/ok-to-test sha=654c946e |
…tos/external-secrets into feat/parametertier_pushsecrets_3422
vsantos
changed the title
vsantos
changed the title
vsantos
force-pushed
the
feat/parametertier_pushsecrets_3422
branch
2 times, most recently
from
6609c5e
to
6728032
Compare
|
This was referenced Jun 19, 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.
Problem Statement
Currently, we don't have the option to set which parameter tier to use for the AWS parameter store, and as a result, all secrets are stored using the default tier
Standard. This PR adds the possibility to work with parameter tierAdvancedand all its policies.Related Issue
Fixes #3422
Checklist
git commit --signoffmake testmake reviewable