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 Secrets Manager Add-on does not get automatically triggered on vault push #346

Open
taylorkangbeck opened this issue Jun 28, 2024 · 3 comments

Comments

@taylorkangbeck
Copy link

I've set up the AWS Secrets Manager Add-on, but after updating values in my vault the changes did not propagate to AWS Secrets Manager. I do see the updated values in the dotenv-vault web UI, but the add-on logs show no movement. I also don't see a way to manually trigger the add-on either, so the only way to push was to delete and re-create the add-on entirely.

@sogos
Copy link

sogos commented Jul 12, 2024

I would also like to report that I encountered the same issue today after a push. As a result, there was no synchronization with AWS Secrets Manager.

@lumariaap15
Copy link

Same with AWS Parameter Store Add-on

@kifah1989
Copy link

Same issue for me. I get "Your secret value has been updated" green banner in AWS secrete manager but cant see the newly pushed env using the command
npx dotenv-vault@latest push

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants