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

Optionally add template outputs to Parameter Store #3

Open
benkehoe opened this issue Oct 25, 2019 · 0 comments
Open

Optionally add template outputs to Parameter Store #3

benkehoe opened this issue Oct 25, 2019 · 0 comments

Comments

@benkehoe
Copy link
Owner

This app can be deployed once to an account and used by multiple state machines. Any code that uses the app shouldn't have to hardcode the Lambda function name or API Gateway URL. So there should be a way to store those values to let that code look up the values for a centrally-deployed instance of this app.

This must be opt-in. If someone is using the SAR app embedded in their own CloudFormation template, the app should stay "local" to that stack, as there may be many instances of the app deployed and they should not all attempt to write their outputs to that central place.

Parameter Store is a good option for this; the lookup is then possible for code deployed directly or using CloudFormation. It would be nice to use CloudFormation exports as well, but these cannot be made conditional at this time.

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

1 participant