This is a summary of recent work for orchestration template for QE to test before the release of 5.9.0 OrchestrationTemplate subclasses for Cloudformation, Heat, and Azure have been renamed. Existing customers should be able to continue to use their templates after they migrate the database. The following changes and new features should be paid more attention while testing. 1. We have a new tool to generate service dialogs from orchestration templates. The resulting dialogs looks the same as before, except for a few enhancements: 1.1 Dialogs from Cloudformation templates are different from the ones from Heat templates. Cloudformation dialogs have more options as described in https://bugzilla.redhat.com/show_bug.cgi?id=1385712. In the original BZ the new options were supported in backend but required user to modify the dialog. Now the options are available from the auto generated dialog. 1.2 Additional parameter data types are supported for Cloudformation templates. Here is the complete list of data type and their appearance in dialog 1.2.1 String -> textbox 1.2.2 Number -> textbox (number only) 1.2.3 List<Number> -> text area box (one number per line) 1.2.4 CommaDelimitedList -> text area box (one string per line) 1.2.5 AWS type, for example, AWS::EC2::KeyPair::KeyName -> text area 1.2.6 AWS type list, for example, List<AWS::EC2::Subnet::Id> -> text area box (one per line) The template containing such parameter types with and without default values should be tested. 1.3 Additional parameter data types are supported for OpenStack. 1.3.1 string -> textbox 1.3.2 number -> textbox (number only) 1.3.3 json -> text area box (formatted JSON string in multiple lines) 1.3.4 comma_delimited_list -> text area box (one string per line) 1.3.5 boolean -> text area box (“t”, “true”, “on”, “y”, “yes”, or “1” for true value and “f”, “false”, “off”, “n”, “no”, or “0” for false value.) Te template containing such parameter types with and without default values should be tested. The original BZ for this enhancement is https://bugzilla.redhat.com/show_bug.cgi?id=1489908 2. Cloudformation templates now support both JSON and YAML formats. Here is the RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1417021. This means any Cloudformation templates in either case will appear under service -> catalog -> orchestration templates -> Cloudformation. Also when you start a blank Cloudformation template, in the editor you can type either JSON or YAML format. 3. Heat templates now support both YAML and JSON formate. Same as above.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set the severity to Low.
Related GitHub pull requests: https://github.com/ManageIQ/manageiq/issues/15985
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-2018:0380