Aws secretsmanager additions#6381
Conversation
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
Signed-off-by: Nick Richardson <nicholas.richardson@akasa.com>
a4701ef to
23175d8
Compare
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
zroubalik
left a comment
There was a problem hiding this comment.
Looking good, thanks. We should also update docs
Doc for issue: kedacore/keda#5940 PR: kedacore/keda#6381 Signed-off-by: michael pechner <mike.pechner@akasa.com>
|
docs. kedacore/keda-docs#1508 |
JorTurFer
left a comment
There was a problem hiding this comment.
Really nice job! some comments inline
tests/secret-providers/aws_secretmanager/aws_secretmanager_test.go
Outdated
Show resolved
Hide resolved
tests/secret-providers/aws_secretmanager_pod_identity/aws_secretmanager_pod_identity_test.go
Outdated
Show resolved
Hide resolved
36f2dcc to
a6b4067
Compare
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
…-akasa/keda into aws-secretsmanager-additions
…ect. Will remove REMOVETestAwsSecretManagerJSONFormat and change aws_secret_manager_pod_identity.go once I have changed this file as expected. Signed-off-by: michael pechner <mike.pechner@akasa.com>
// Local imports . "github.com/kedacore/keda/v2/tests/helper" Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
|
e2e tests are failing because the secret has the same name in both cases. This makes that one case passes and the other one fails because the e2e test is trying to create a secret with the same name and the secret is in deletion process You can't create this secret because a secret with this name is already scheduled for deletionYou need to update the value of |
…e the secret. Instead of tryinfg to further randomize the secretname, just let the code do what it should. Added a poll to wait on the secret to be removed. Hoping 2 minniutes is more than enough. Signed-off-by: michael pechner <mike.pechner@akasa.com>
…e the secret. Instead of trying to further randomize the secretname, just let the code do what it should. Added a poll to wait on the secret to be removed. Should happen within a few seconds. But we are talking AWS. 5 minutes really should be more then enough. Signed-off-by: michael pechner <mike.pechner@akasa.com>
…-akasa/keda into aws-secretsmanager-additions
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: michael pechner <mike.pechner@akasa.com>
tests/secret-providers/aws_secretmanager_pod_identity/aws_secretmanager_pod_identity_test.go
Outdated
Show resolved
Hide resolved
made sure we set a new secret name for each run Signed-off-by: michael pechner <mike.pechner@akasa.com>
Signed-off-by: Michael D Pechner - Akasa <mike.pechner@akasa.com>
JorTurFer
left a comment
There was a problem hiding this comment.
Really great job! 2 small comments inline and we are almost there!
tests/secret-providers/aws_secretmanager/aws_secretmanager_test.go
Outdated
Show resolved
Hide resolved
tests/secret-providers/aws_secretmanager_pod_identity/aws_secretmanager_pod_identity_test.go
Outdated
Show resolved
Hide resolved
|
/run-e2e aws |
Signed-off-by: michael pechner <mike.pechner@akasa.com>
|
/run-e2e aws |
tests/secret-providers/aws_secretmanager/aws_secretmanager_test.go
Outdated
Show resolved
Hide resolved
tests/secret-providers/aws_secretmanager_pod_identity/aws_secretmanager_pod_identity_test.go
Outdated
Show resolved
Hide resolved
Signed-off-by: michael pechner <mike.pechner@akasa.com>
…-akasa/keda into aws-secretsmanager-additions
|
/run-e2e aws |
|
/run-e2e aws |
|
/run-e2e aws |
…1508) * Documented adding secretKey parameter to access aws secret manager Doc for issue: kedacore/keda#5940 PR: kedacore/keda#6381 Signed-off-by: michael pechner <mike.pechner@akasa.com> * Added a note to the description for the secretKey parameter and entry to the example for the parameter. Signed-off-by: michael pechner <mike.pechner@akasa.com> --------- Signed-off-by: michael pechner <mike.pechner@akasa.com>
This adds the ability to specify a secretKey in the awsSecretManager TriggerAuthentication. This will allow parsing of secrets that contain Key/Value pairs (returned in JSON format).
Resubmission of #6031
Provide a description of what has been changed
Checklist
Fixes #5940
Relates to #