add create_catalog_item to ServiceTemplateAnsibleTower

[jntullo]

This adds class method create_catalog_item to ServiceTemplateAnsibleTower and takes in the following:

      {
        :name         => 'Ansible Tower',
        :service_type => 'generic_ansible_tower',
        :prov_type    => 'amazon',
        :display      => 'false',
        :description  => 'a description',
        :config_info  => {
          :configuration_script_id => configuration_script.id,
          :provision               => {
            :fqname            => ra1.fqname,
            :dialog_id => service_dialog.id
          },
          :retirement              => {
            :fqname            => ra2.fqname,
            :dialog_id => service_dialog.id
          }
        }
      }

@miq-bot add_label wip, enhancement, orchestration, services, euwe/no
@miq-bot assign @bzwei

[bzwei]

We want to accept :configuration_script_id or :configuration. The later points to an object that can be directly assigned. Same to manager. Need to update the validate method too.

[jntullo]

@miq-bot remove_label wip

[mkanoor]

@jntullo
Wouldn't a single service template have a job template per resource action (provision, reconfigure, retirement).
Its not a one to one relationship, I think its 1 to max 3 job templates.

[bzwei]

@mkanoor this is the refactoring work for existing AnsibleTower. The work you're interested is #13600

[bzwei]

@miq-bot assign @gmcculloug

[gmcculloug]

@jntullo This method does not appear to differ from the one in the parent ServiceTemplate model here: app/models/service_template.rb#create_resource_actions

Is this really needed?

[bzwei]

You're right. It should not be needed. Good catch.

[miq-bot]

Checked commits jntullo/manageiq@51f4ac3~...22fa778 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks good. 🍰