-
Notifications
You must be signed in to change notification settings - Fork 12
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
[CT-578] Add aws secret for db password #97
Conversation
indexer/locals.tf
Outdated
@@ -19,7 +19,7 @@ locals { | |||
} | |||
|
|||
service_secret_ids = { | |||
for name in local.service_names : name => "${var.environment}-${name}-secrets" | |||
for name in local.service_names : name => "${var.aws_db_secret_id}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this change made so that a deployer could determine what secret to create in secrets manager before deploying?
There's other secrets that exist today, this could break deployments that had diff. secret ids right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, there's existing dev-vulcan-secrets/dev-ender-secrets/etc. We'll need to add db_password into these secrets manually. Env variables are encrypted & passed into lambdas.
tested in dev