-
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
Support for overriding parameters in AWSFNCLI #52
Comments
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stackinstances-override.html |
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? |
@GlieseRay I think he is asking for |
Hi,
Yes this is in reference to Stacksets
Best Regards
Allan Smeyatsky
… On 21 Oct 2018, at 16:33, Kotaimen ***@***.***> wrote:
@GlieseRay I think he is asking for StackSet support?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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. |
Thank you so much for the response!
Best Regards
Allan Smeyatsky
… On 22 Oct 2018, at 05:10, Kotaimen ***@***.***> wrote:
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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No description provided.
The text was updated successfully, but these errors were encountered: