We have a Habitat application that has tried to setup a supervisor ring with their service set to be rolling strategy. This allows when a package is promoted to the channel that all the peers do have a rolling restart as expected. Although, when they do a hab config apply toml configuration to one of the remote supervisors it applies the toml to all the nodes in the ring at the same time instead of it being a rolling strategy. The service is being restarted and the init hook executing at the same time which is causing an outage to the application.
We were told that this is the expected behavior. the strategies are related to updates and not configuration.
We would like an enhancement for it to be applied to configuration in a rolling strategy.