Description of problem: Today, bin/ambari_config_update.sh only supports append and prepend actions, and is used only to update the "fs.glusterfs.volumes" core-site property value. A companion script, ambari_config.sh (with lots of duplicate code) is invoked to add the "fs.glusters.volume.fuse.<name>" property and value. It will be easier to maintain these scripts if the 2 are combined and all action verbs are supported. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New actions add, delete, remove, and replace (in addition to the existing append and prepend) are now supported by bin/ambari_config_update.sh. bin/ambari_config.sh is no longer being used.
I think that goals for this bug are: 1) merge 2 scripts -> this was not accomplished because user cannot get current value of key from configuration(ambari_config.sh functionality by getting whole config. file), user cannot get config. file content(ambari_config.sh functionality) 2) There is no documentation about what actions mean. I understand what do these actions: add|delete|prepend|append|replace But I was not able to understand what does remove. State: "key1": "value5" I've tried: ./ambari_config_update.sh --configkey key1 --action remove --cluster TestCluster --configvalue "value5" No change. ./ambari_config_update.sh --configkey key1 --action remove --cluster TestCluster --configvalue "value3" WARN: value3 not present in key1; no action needed ./ambari_config_update.sh --configkey key1 --action remove --cluster TestCluster ..help message.. What is purpose of this action, please?
Martin, I am unsure what you are asking in comment 7. Version 2.36 will remove all occurrences of the passed-in value from the passed-in key with --action remove. However, the assumption is that the prop value is a list of tokens separated by a single comma and no white-space.
Ok, I filed bug 1163669 for removing and verify this BZ.
Jeff, Could you please provide the doc text in the Doc Text field for this bug?
Jeff, Could you please review the edited doc text for technical accuracy and sign-off?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2014-1275.html