generated from TBD54566975/tbd-project-template
-
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
Sync asm secrets with db resolver references #2104
Comments
Open
That's a great idea |
Alternative: introduce a command to attach an existing asm secret to a db ref, to allow client teams to bring in refs more intentionally. i.e. from @bradleydwyer:
|
The team does not think there is work to be done here if we incrementally update the db instead of performing wipes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, nuking / recreating the db removes all references to asm secrets, which means all secrets need to be set again. Client team has had to do this a few times.
Since we're tagging all asm secrets with "ftl", we can fetch them and add their refs to the db. Perhaps at first load / if we have zero refs?
The text was updated successfully, but these errors were encountered: