-
Notifications
You must be signed in to change notification settings - Fork 120
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
Tag migrated VM. #324
Tag migrated VM. #324
Conversation
@miq-bot add_label enhancement, transformation |
@fdupont-redhat Please review/test |
@@ -28,8 +28,9 @@ def main | |||
exit MIQ_OK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, the code exits right at the beginning of main
. If we want the tag assignment to be active, the exit MIQ_OK
statement should be placed after source_vm.tag_with(...)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To take this a step further it would be better to remove the exit MIQ_OK
line completely and change this method to only do the tagging.
The other logic should either be removed or at the least moved into a new method in this script.
@fdupont-redhat Are there plans to use this logic soon? If not let's remove the unused code.
cc @mkanoor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gmcculloug, no plan to change it soon, so yes it can be remove. It will be cleaner.
fde0733
to
79dfbbe
Compare
Checked commit lfu@79dfbbe with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
@fdupont-redhat Don't want to lose the question from the hidden comment #324 (comment)
|
@gmcculloug, no plan to change it soon, so yes it can be removed, or simply
moved in a dedicated method. It will be cleaner.
…On 6 June 2018 at 18:49, Greg McCullough ***@***.***> wrote:
@fdupont-redhat <https://github.com/fdupont-redhat> Don't want to lose
the question from the hidden comment #324 (comment)
<#324 (comment)>
@fdupont-redhat <https://github.com/fdupont-redhat> Are there plans to
use this logic soon? If not let's remove the unused code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#324 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYoAaEkMGC12jpou2JbN3a_vSG9_uTMIks5t6AgbgaJpZM4UcnXJ>
.
--
*Fabien Dupont*
PRINCIPAL SOFTWARE ENGINEER
Red Hat - Solutions Engineering
[email protected] M: +33 (0) 662 784 971 <+33662784971>
<http://redhat.com> *TRIED. TESTED. TRUSTED.*
Twitter: @redhatway <https://twitter.com/redhatway> | Instagram: @redhatinc
<https://www.instagram.com/redhatinc/> | Snapchat: @redhatsnaps
|
@@ -28,8 +28,9 @@ def main | |||
exit MIQ_OK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gmcculloug, no plan to change it soon, so yes it can be remove. It will be cleaner.
Tag migrated VM. (cherry picked from commit d7d3f5d) https://bugzilla.redhat.com/show_bug.cgi?id=1590430
Gaprindashvili backport details:
|
Part of ManageIQ/manageiq#17389.
https://bugzilla.redhat.com/show_bug.cgi?id=1565199