I am working on the provider refresher code to suppress resource groups from OpenStack being read as nested stacks. As a result no additional heat templates will be added to VMDB.
After more discussions we decide to introduce a new column named orderable to orchestration template table. Templates that are found in provider but not in VMDB will be marked as not-orderable, thus not visible in Service -> Catalogs -> Orchestration Templates. User added templates through manageiq UI template editor will be visible. Templates that are found in provider but identical to the ones added by user will remain visible too.
https://github.com/ManageIQ/manageiq/pull/6538
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/808f553d23d51bf9ed6d9aa9ca1865513437df65 commit 808f553d23d51bf9ed6d9aa9ca1865513437df65 Author: Bill Wei <bilwei> AuthorDate: Fri Feb 5 09:19:57 2016 -0500 Commit: Bill Wei <bilwei> CommitDate: Thu Feb 11 16:57:21 2016 -0500 Add orderable column to orchestration_templates User added templates are default to orderable. Auto collected templates from provider are default to non-orderable. https://bugzilla.redhat.com/show_bug.cgi?id=1302810 app/controllers/catalog_controller.rb | 6 +- .../amazon/cloud_manager/refresh_parser.rb | 1 + .../azure/cloud_manager/refresh_parser.rb | 3 +- .../refresh_parser_common/orchestration_stacks.rb | 3 +- app/models/orchestration_template.rb | 42 ++++++++-- ...130_add_orderable_to_orchestration_templates.rb | 15 ++++ .../amazon/cloud_manager/refresher_spec.rb | 1 + spec/models/orchestration_template_spec.rb | 92 ++++++++++++++++++---- 8 files changed, 136 insertions(+), 27 deletions(-) create mode 100644 db/migrate/20160203101130_add_orderable_to_orchestration_templates.rb
Reassign to UI to complete the rest of the changes. https://github.com/ManageIQ/manageiq/issues/6600
https://github.com/ManageIQ/manageiq/pull/7822
Fixed. Verified in 5.6.0.5-beta2.4.20160503153816_1fb554f Orchestration templates are orderable and not visible unless ordered
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/RHBA-2016:1348