Similar to Zookeeper Quorum, if the topology of Atlas Servers changes (move, delete, add), then Stack Advisor needs to recalculate atlas.rest.address property in atlas-application.properties
The value is a csv of http(s):$server:$port for each Atlas Server.
Today, the configuration files can only specify config-to-config dependencies, so there is no config-to-component dependency.
This means that today the UI has config initializers to make changes to properties like hbase.zookeeper.quorum and nimbus.seeds
Is this feasible in Ambari 2.4? Once this is done, we need to prevent the UI from editing atlas.rest.address after the cluster is deployed, since only Stack Advisor will allow calculating the value, so we may need the correct values for editable-only-at-install, overridable, read-only in the config file.