-
Notifications
You must be signed in to change notification settings - Fork 20
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
add support for stack policies (create and override) #40
Conversation
LGTM. I'd like someone more familiar with using cf_deployer to check this over too, though, as I've never used it for anything. |
the travis failure looks like travis itself or a ruby gem thing, not the changee. I don't see the little icon to rebuild. I thought travis had that? |
@@ -82,7 +82,15 @@ Used by the gem for blue/green deployments and naming conventions | |||
* keep-previous-stack (True/False: for Cname-Swap and Auto Scaling Group Swap, previous stack will be kept after new stack is created by default. Set it to false to delete the previous stack) | |||
* raise-error-for-unused-inputs (True/False: it is false by default. If it is set to true, errors will be thrown if there are any inputs which are not used as parameters of CloudFormation json templates. If it is set to false or the setting does not exist, warnings will be printed in the console if there are un-used inputs.) | |||
* auto-scaling-group-name-output | |||
* **For Components Using the Cname-Swap Deployment Strategy** | |||
* create-stack-policy-filename: the name of the json file (w/o the json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thinking these setting shouldn't have "filename" in the name. to be consistent with how cf_deploy works, i.e. the file'ness and location of these should be inferred relative to the config dir. change coming up shortly to remove "-filename" from the setting names...
…ployer - better explanation in docs of usage of the override policy
Looks good |
@kmanning @jantman