Hi, Ideally the underlying service would have a single toggle for Kerberos, rather than require the administrator / administrative tool know that several configs must be changed at the same time. If that's not possible, then you can implement this in the bash script. There's many approaches to doing this, but in the simplest case, you can essentially: 1) Have a single parameter to control kerberos, let's say it's a boolean "kerberos.enabled". 2) In the SDL, have the kerberos section reference this parameter "kerberos" : "${kerberos.enabled}", 3) Emit an environment variable "roles": [
{
"name": "EXAMPLE_ROLE",
// ...
"startRunner": {
// ...
"environmentVariables": {
"KERBEROS_ENABLED" : "${kerberos.enabled}",
// ... 4) In your control script, check the value of $KERBEROS_ENABLED, and then add configs to the XML accordingly. One nice way to accomplish the last step is to use additionalConfigs to create a placeholder value, then use perl to replace it. So your SDL would have: "roles": [
{
"name": "EXAMPLE_ROLE",
// ...
"configWriter": {
"generators": [
{
"filename": "example.xml",
// ...
"additionalConfigs" : [
{
"key" : "kerb.prop.a",
"value" : "{{KERB_PROP_A}}"
},
{
"key" : "kerb.prop.b",
"value" : "{{KERB_PROP_B}}"
},
// ... Then your control script would implement the conditional logic you need, then replace those variables: if [[ ${KERBEROS_ENABLED} == "true" ]]; then
KERB_PROP_A=1
KERB_PROP_B=2
else
KERB_PROP_A=100
KERB_PROP_B=121
fi
perl -pi -e "s#\#{{KERB_PROP_A}}#${KERB_PROP_A}#" "$CONF_DIR/example.xml"
perl -pi -e "s#\#{{KERB_PROP_B}}#${KERB_PROP_B}#" "$CONF_DIR/example.xml" Thanks, Darren
... View more
