In application development framework the application may report its "configuration key", i.e. signature of application's configuration. If it hasn't been changed since the previous deployment it does not get re-applied during subsequent deployments.
It should not affect the new nodes added to server group (e.g. by a scale out action), however for now it affects them: when a new node is spawaned and if the configuration key is overriden, the configuration is not applied on new nodes.
In application development framework the application may report its "configuration key", i.e. signature of application's configuration. If it hasn't been changed since the previous deployment it does not get re-applied during subsequent deployments.
It should not affect the new nodes added to server group (e.g. by a scale out action), however for now it affects them: when a new node is spawaned and if the configuration key is overriden, the configuration is not applied on new nodes.