add config secret resources to iac and modularize #243
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
• Does any part of it require special attention?
• Does it relate to or fix any issue?
this is a follow up to #242
In this pr we add the new term SecretsManagerSecrets to our aws template and we take the name and the path for the file which contains the value.
For our current secrets, since the secret name is the path we set that for the values file. For config resources right now we leave it empty.
For config resources since we see theres no values file we prompt for the path in pulumi config to create it.
This modularizes the secrets manager iac code so we optionally add it to output and just construct the class
Standard checks