-
Notifications
You must be signed in to change notification settings - Fork 897
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
Use human friendly names in task names and notifications for Tower CUD operations #14977
Conversation
This pull request is not mergeable. Please rebase and repush. |
Checked commits jameswnl/manageiq@f30670a~...d2636d3 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@chrispy1 unrecognized command 'blocker', ignoring... Accepted commands are: add_label, assign, close_issue, move_issue, remove_label, rm_label, set_milestone |
@miq-bot add_label blocker |
@miq-bot add_label fine/yes |
Use human friendly names in task names and notifications for Tower CUD operations (cherry picked from commit d7c3613) https://bugzilla.redhat.com/show_bug.cgi?id=1440573 https://bugzilla.redhat.com/show_bug.cgi?id=1449223
Fine backport details:
|
A further improvement on top of #14656 for https://bugzilla.redhat.com/show_bug.cgi?id=1439203
and for https://bugzilla.redhat.com/show_bug.cgi?id=1448081 as well.
Use human friendly names instead of the class names in task names and keep the notification message brief and user friendly.
Before:
e.g.
Creating ManageIQ::Providers::AnsibleTower::AutomationManager::ConfigurationScriptSource name=My repo
The operation ConfigurationScriptSource update_in_provider {:name=>..... create_on.....} completed successully
Now:
e.g.
Creating Ansible Tower Project (name=My repo)
The operation Ansible Tower Project update (name=My Repo, manager_ref=1) on Tower(manager_id=10000000) completed successfully.
@miq-bot add_labels bug, providers/ansible_tower