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
CloudFormation Deploy - Warning for no changes #91
Comments
Sure, we'll take a look. |
Implemented with a new task option, 'Log warning during stack update if AWS CloudFormation reports no work to be done' (default checked). This will be included with the next update which is in the final stages of i-dotting and t-crossing. |
Awesome. Thanks for the quick work! I'll be on the lookout for it. |
Resolving, included in v1.1.0 released Aug 2nd. |
I'm not sure if this change broke the changes done for issue #28 but now if I deploy a stack that uses a change set and there are no changes I get an error and the release fails. I didn't notice any options that I could change other than the "Log warning during stack update..." that was added for this issue (#91). There is a "Continue on error" option under Control Options but I don't think we want to do that in case there are other issues with the CF deployment. The deployment without a change set works as expected.
|
We're using the CloudFormation Create/Update Stack task (without a Change Set) in VSTS. Is it possible to not log a warning when there's no changes to a CloudFormation stack on deployment? Even if we had the option to turn it on or off it would be helpful.
With the new VSTS UI it shows the phase as having 1 issue even if it's a warning, which I personally don't like either, but having a warning show for something that's perfectly fine seems a bit misleading to us.
I do see why it was originally put in ( see #28 ) but it would be nice to be able to have a release without any issues showing when it's finished if possible.
The text was updated successfully, but these errors were encountered: