[WIP] Set manager_ref to file path for embedded ConfigurationScripts #711
Conversation
agrare
changed the title
The manager_ref is typically used to track the "unique" attribute of an object, for ansible_tower/awx the manager_ref is the job_template.id but for embedded_ansible the manager_ref was nil and the name was set to the file path. Embedded Workflows copied this behavior, but it would be preferable to match how the "external" automation managers operate and also open up the `:name` column for a more user friendly name.
agrare
force-pushed
the
set_manager_ref_embedded_configuration_scripts
branch
from
5ee9c1d
to
3e33249
Compare
|
Checked commit agrare@3e33249 with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
2 similar comments
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
|
This pull request has been automatically marked as stale because it has not been updated for at least 3 months. If these changes are still valid, please remove the |
The manager_ref is typically used to track the "unique" attribute of an object, for ansible_tower/awx the manager_ref is the job_template.id but for embedded_ansible the manager_ref was nil and the name was set to the file path.
Embedded Workflows copied this behavior, but it would be preferable to match how the "external" automation managers operate and also open up the
:namecolumn for a more user friendly name.