Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aws secretsmanager additions #6031

Conversation

nrichardson-akasa
Copy link

@nrichardson-akasa nrichardson-akasa commented Aug 2, 2024

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).

Checklist

Fixes #
#5940

Relates to #

Signed-off-by: Nick Richardson <[email protected]>
Signed-off-by: Nick Richardson <[email protected]>
@nrichardson-akasa nrichardson-akasa marked this pull request as ready for review August 6, 2024 22:34
secrets:
- parameter: connection
name: {{.SecretManagerSecretName}}
secretKey: connectionString
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This indentation does not show up on my machine. Not sure why it is here

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it produces e2e failures :( Could you fix it? Maybe you need to make 2 commits as usually tabs and whitespace are ignored depending on config

@zroubalik
Copy link
Member

zroubalik commented Aug 7, 2024

/run-e2e secret-providers
Update: You can check the progress here

Copy link

stale bot commented Oct 19, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Oct 19, 2024
Copy link

stale bot commented Oct 28, 2024

This issue has been automatically closed due to inactivity.

@stale stale bot closed this Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale All issues that are marked as stale due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants