-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support provider name & template name to uniquely identify a template #11669
Conversation
Just noted this PR in the bug, I was wondering why is provider name better than provider ID? Provider ID (or GUID) cannot change for one given provider but name can. |
@mfalesni When you specify a template you can pass one of the following to uniquely identify a job template
This PR adds option 3 from above. |
@bzwei Please review |
@mkanoor should the provider name key |
https://bugzilla.redhat.com/show_bug.cgi?id=1378606 Optionally support 'ansible_provider_name' to uniquely identify a job template. This is needed where you might have multiple Ansible Towers with the same named templates.
47c0533
to
bcf2a67
Compare
bcf2a67
to
4fc0d67
Compare
Checked commits mkanoor/manageiq@23f8ac3~...4fc0d67 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 db/fixtures/ae_datastore/ManageIQ/ConfigurationManagement/AnsibleTower/Operations/StateMachines/Job.class/methods/launch_ansible_job.rb
|
@bzwei |
@mkanoor definitely we should simplify the spec. I am OK with a separate PR. |
Support provider name & template name to uniquely identify a template (cherry picked from commit 76c643b) https://bugzilla.redhat.com/show_bug.cgi?id=1411359
Euwe backport details:
|
Optionally support 'ansible_provider_name' to uniquely identify a
job template. This is needed where you might have multiple Ansible
Towers with the same named templates.
Links
Testing:
Bugzilla provides the details