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

Support for overriding parameters in AWSFNCLI #52

Open
asmeyatsky opened this issue Oct 15, 2018 · 6 comments
Open

Support for overriding parameters in AWSFNCLI #52

asmeyatsky opened this issue Oct 15, 2018 · 6 comments
Assignees

Comments

@asmeyatsky
Copy link

No description provided.

@asmeyatsky
Copy link
Author

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stackinstances-override.html
Hi, please advise when AWSFNCLI might support over riding parameters
TY
Allan

@asmeyatsky asmeyatsky changed the title Support for Support for overriding parameters in AWSFNCLI Oct 15, 2018
@GlieseRay
Copy link
Collaborator

Hi @asmeyatsky , Do you mean overriding parameters in the awscfncli config file? If it is , you can use a blueprint to wrap up your common attributes and override them in each deployment stages (including stack parameters and metadata such as region and account profile). There is a sample in the REAMDME. If not, can you give a more specific description of your use case?

@Kotaimen
Copy link
Owner

@GlieseRay I think he is asking for StackSet support?

@asmeyatsky
Copy link
Author

asmeyatsky commented Oct 21, 2018 via email

@Kotaimen
Copy link
Owner

Hi @asmeyatsky,

We'll consider add StackSet support in 2.2 or 2.3 release.

However you can use the cfn-cli config to mimic StackSet by deploying a stack in different account and regions. We are also going to release 2.1 soon, adds support of cross-account stack output reference, which StackSet does not support.

@asmeyatsky
Copy link
Author

asmeyatsky commented Oct 22, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants