Sumit Mohanty created AMBARI-20136: -------------------------------------- Summary: Services should be able to specify that credential store is always enabled Key: AMBARI-20136 URL: https://issues.apache.org/jira/browse/AMBARI-20136 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Priority: Critical Fix For: 2.5.0
At this point, credential store can be enabled or disabled for a service. Some services, such as Ranger and LogSearch should be able to indicate that CS cannot be disabled. The eventual goal is to always have CS enabled for all services that support credential store. Current metainfo.xml has the following section {code} <credential-store> <supported>true</supported> <enabled>false</enabled> </credential-store> {code} We need to add a notion of required. A third element called "required" may be added. We can potentially, create an enum for a new field "supportType" and collapse "supported" and "required" but that, while succinct, does not help much in readability. {code} <credential-store> <supported>true</supported> <required>false</required> <enabled>false</enabled> </credential-store> {code} The above means, CS is supported, not required, and not enabled. "false" is the default for *required*. For services that require CS support {code} <credential-store> <supported>true</supported> <required>true</required> <enabled>true</enabled> </credential-store> {code} Service create logic should set the CS-enabled flag to be true if *required* is true independent of what *enabled* says. *required* flag is not needed in the service resource REST API but the stacks API should provide access to this flag. API to disable CS should throw an error if *required* is true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)