Hi Rob, I do not think this is by design. I think it is so today because 'cluster-env' is not managed by any of the traditional services in stack.
Actually 'cluster-env' config-type is sent from UI when doing 'configurations-validation'. We just need to make sure to send it up when doing any of 'configuration-recommendation', 'component-layout' and 'component-validation'. UI should be able to send this everytime a call is made - please open a JIRA for this. Best regards Srimanth ________________________________ From: Robert Levas Sent: Thursday, June 30, 2016 6:13 AM To: Srimanth Gunturi; [email protected] Cc: [email protected] Subject: Recommendations API, Stack Advisor, and cluster-env Srimanth, Tom, devs... Does anyone know why we don't send in the cluster-env config when querying for recommendations via REST API? This call makes its way into the stack advisor and appears to have every (relevant) config type, except for cluster-env. Since the API call is not relevant to a cluster, the data cannot be looked up and thus must be supplied by the caller. I think that this may be a bug (possibly in the UI), but maybe it is by design for some reason. In any case, cluster-env contains some import information that may be relevant for decisions made by the stack advisor. For example, I am looking to have the stack advisor make decisions based on whether Kerberos is enabled or not. This data is stored in cluster-env/security_enabled, where true indicates Kerberos is enabled and false indicates that Kerberos is not enabled. Rob
