We are in the process of re-evaluating all RFEs, for the short-term, anything in unspecified is getting set to a low priority. In the coming weeks, these will all be reviewed and re-prioritized to something that closer reflects reality.
Brad - Can you confirm this request apply only to Automate -> Customization -> Buttons. I do not think this would include custom buttons for Service Templates. Erik - Here is an example from the rh-consulting scripts that we can evaluate for this purpose: https://github.com/rhtconsulting/cfme-rhconsulting-scripts/blob/master/rhconsulting_buttons.rake
Correct, buttons on service templates should be in another request.
https://github.com/ManageIQ/manageiq/pull/17726 and https://github.com/ManageIQ/manageiq/pull/17699 are the starts
Brad - Question on the implementation: If a existing custom button already exists in the database should we update or skip as the default action during import? (The same question applies to the group.)
I would like for the script to have an overwrite option. Default does not overwrite however if the flag is there then overwrite.
https://github.com/ManageIQ/manageiq/pull/17699 got merged, so just waiting on final comments on 17726
Need to address the overwrite option in subsequent PRs but closing this as post because the two PRs needed for the main functionality have been merged
I tested it with 5.10 latest steps: 1. Create custom buttons with different object types 2. Verify buttons and respective groups 3. ssh appliance 4. create one temp dir (suppose /tmp/custom_buttons) 5. export with the following command: rake evm:export:custom_buttons -- --directory /tmp/custom_buttons 6. either delete available buttons and groups or just take a new appliance and transfer file created in the temp dir 7. ssh to the new appliance 8. Import with the following command: rake evm:import:custom_buttons -- --source /tmp/custom_button/exported_custom_buttons.yaml 9. Check for all exported customs button comes in UI or not. It's working awesome.
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://access.redhat.com/errata/RHSA-2019:0212