cloudposse
add ability to write secrets for amplify app
what
Amplify can access secrets during build and runtime This PR allows the
why
It may be useful depending on a user's secrets management pattern to write secrets here when creating the amplify app.
references
https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#environment-secrets fixes #31
![mergify[bot] avatar](https://avatars.githubusercontent.com/in/10562?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR was closed due to inactivity and merge conflicts. 😭 Please resolve the conflicts and reopen if necessary.
@kevcube, why can't a secret be written externally based on the module's outputs after the Amplify app is created?
It can be written externally, if someone wants to use remote-state or something to grab the amplify ID that's an option, but because amplify has the ability to access secrets stored at these predefined paths I thought it made sense to package in this module because they can be considered a part of the amplify application stack
@kevcube, why can't a secret be written externally based on the module's outputs after the Amplify app is created?
@goruha do you have a reason why it should not be included in this module?
This PR was closed due to inactivity and merge conflicts. 😭 Please resolve the conflicts and reopen if necessary.