-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use MaxResults/pagination for list_secrets in AWS Secrets Manager - or switch to describe_secret instead #107
Labels
enhancement
New feature or request
Comments
@KiraLT - Thanks for the update - but... the v0.4.0 build zip file seems to be a bit broken. After upgrading I get this error in AWS Lambda.
|
FYI I am also getting this Thanks for the work, this saved me a bunch of time :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
services/aws.py:list_secret_names()
there is no MaxResults nor any pagination code - so in any account with a lot of secrets, it may not return the secret being used - which will then cause create_or_update_secret() to fail creating a new secret instead of updating the existing one.Alternatively, could refactor the code to call
describe_secret
instead oflist_secrets
as this would reduce the IAM policy requirements and also fix pagination issues at the same time.Thanks, this tool is really helpful :)
The text was updated successfully, but these errors were encountered: