DaanHoogland commented on PR #6809: URL: https://github.com/apache/cloudstack/pull/6809#issuecomment-1366666453
> > @wido @soreana , we don´t have true granularity, but we can, if the scope is cluster, edit at global level a vaule that will then function as a default on cluster level. No need to keep the global level to be able to set it globally. I think though, that the global level will only function as default to those clusters that have not set it yet. I am not sure about the reset. > > @DaanHoogland, regarding the behavior of the configurations, once we change a configuration on cluster level or another scope (except global), an entry in `cloud.<X>_details` (`cluster_details` for `Cluster`, `data_center_details` for `Zone`, and so on) is persisted, and then, for that scope, this entry will guide the behavior instead of the entry in `cloud.configurations` (global level). For resetting those configurations to the global (default) value, we can use the API [resetConfiguration](https://cloudstack.apache.org/api/apidocs-4.17/apis/resetConfiguration.html). Exactly, which should be good enough. Editing the global level should set the default on a scoped level. It might be that a scoped level that has not set this setting, keeps using the default value from the global level though, instead of the edited global value. I have not tested that and if it does that would be a bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
