Ray

@andyfase That's a good point. @Kotaimen Maybe we can raise error when user who is using cross-statck reference wants to export config. We need to add proper tests to make...

@Kotaimen I am going to use mustache or something else. Testing.

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...

@Kotaimen will change the implementation in next release to accommodate both 2.7 and 3.6

I am suggesting the following way: 1. Keep default behavior and --confirm for now. Add --no-confirm (default to false) but always set it to true for now. 2. Show warning...

@andyfase Yes Step1: keep default behavior and add --no-confirm default to true, --confirm will override --no-confirm Step2: Warning user that he need to add --no-confirm explicitly if they want to...

@alytle The ${...} is used for stack parameter reference now. So for in config replacement we probably need a new format. But I don't feel that a "ref" structure is...

It could be supported I think. @alytle Do you have any detail workflow or example use case that we could take look ? cc: @Kotaimen

@Kotaimen @alytle Will take a look. we will definitely move to awscli2...

Yes, and looks like they are not going to put it on pypi because of various reasons....