An error occurred (ValidationError) when calling the UpdateStack operation: No updates are to be performed

By -

What is the correct command syntax for checking whether or not a specific call to aws cloudformation update-stack will result in any changes being made?

The problem we are having is that an automation program that runs an aws cloudformation update-stack --stack-name ourstackname --template-body file://c:\path\to\ourtemplate.json --parameters ParameterKey=someKey,ParameterValue=someValue ... command is failing with the following error:

An error occurred (ValidationError) when calling the UpdateStack operation: No updates are to be performed.

The result is a 254 http response code which we can tell from this documentation link means that a lot of possible problems could have occurred. So it would NOT help us to handle that 254 response code.

What aws cloudformation cli command syntax can we type instead to have the automation process receive a 0 response code in cases where no changes will be made? For example, a --flag added to the aws cloudformation update-stack ... command to return 0 when no changes are made.

Alternatively, if there were some preview command that returned 0 indicating that NO CHANGES WILL BE MADE, then our automation could simply refrain from calling aws cloudformation update-stack ... in that situation.

Terraform, for example defaults to simply succeeding while reporting that no changes have been made after a run when presented with this use case.



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more