-
Notifications
You must be signed in to change notification settings - Fork 42
[#369] Inactive migration plans can be scheduled to run #401
[#369] Inactive migration plans can be scheduled to run #401
Conversation
55dc8a2
to
d39f843
Compare
@vconzola any chance yah have the rest of the mockups for this available? (as mentioned here) Other things we're waiting on
🌮 💃 EDIT - yeah, sorry, asking now cuz this has kinda reached the point of highest heights without ☝️ Another Edit - we just gotta get bdunne's pr in then this will be g2g |
2a6a83b
to
54f6bce
Compare
<strong>{plan.name}</strong> | ||
{__(' targted to run on ')} | ||
{moment(plan.schedule_time).format('MMMM Do YYYY, h:mm a')} | ||
{__('?')} |
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.
I am aware the PR is still WIP, but here's the thing that we discussed in the i18n context about complete sentences.
The sentence should ideally look like this -
"Are you sure you want to unschedule plan %s targeted to run on %s?"
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.
Check out https://github.com/ManageIQ/miq_v2v_ui_plugin/blob/9aa142a0b212750cb7affb286654e0c98b49c1e9/app/javascript/react/screens/App/Overview/components/DeleteInfrastructureMappingConfirmationModal/DeleteInfrastructureMappingConfirmationModal.js#L58 for styled, sprintf
implementation.
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.
yeah! thanks for the 👁 🙇 ❤️
1f439db
to
0afbd49
Compare
'Are you sure you want to unschedule plan %s targted to run on %s ?' | ||
), | ||
plan.name, | ||
moment(plan.schedule_time).format('MMMM Do YYYY, h:mm a') |
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.
can this one use our formatDateTime
helper? 🍬
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.
this one yeah! that sounds like a gooooood call
{__(`Migration scheduled`)} | ||
<br /> | ||
{moment(plan.schedule_time).format( | ||
'MMMM Do YYYY, h:mm a' |
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.
same deal w/ the helper
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.
yeah!
0afbd49
to
8a47d69
Compare
Just in case an inquiring mind was wondering... ux is done.... our path to completion is presently then whatever cleanup befalls after the fact... profit 🌮 🥇 |
If it's not much additional work, fine w/ me ;) otherwise, lgtm |
Yah, it'll be some work, can do it later if desired by QE 👍 |
@AllenBW The EDIT: |
@AllenBW This looks really great... the delay however... The delay is noticeable and big enough to get us in this situation - Clicking on the button causes the 500 error Would it be possible to gray out the Schedule and the Unschedule button in the listview until the Plan is actually scheduled/unscheduled? |
@AparnaKarve the notification is thrown as soon as the callback is resolved, as in when the plan is actually Scheduled/unscheduled. The delay is because we poll the page... If the behavior blocks the merging of this pr, I can work on this nowish 🤷♀️ In the defense of leaving it as is for the moment, seems that scheduling while a schedule is already in place, doesn't disrupt the existing schedule, just throws the, "hey there's already something scheduled error" at which point the schedule can be removed and readded 🤔 |
So a few changes come to mind.... we can... (in order of effort, least to most to absolute least)
|
I believe this is indeed kosher :) One of the great things about edit 1: In the documentation, scroll down to So, if you decided to go down this road, I will not complain :) |
yes - of the options you list, it seems like 3 or 4 (calling I should add that I don't think option 1 is really an option - b/c I have heard previously that the backend automate code is only refreshing every 15 seconds, currently...so polling more frequently on the frontend seems like a bad route. |
@michaelkro Thanks for the input! I've been chewing on what ya posted, still very unclear on how this approach might be successfully wired up. If you have some spare cycles would appreciate a pair on this :-/ |
@AllenBW @AparnaKarve This should fix the "Name has already been taken" validation error. ManageIQ/manageiq#17696 |
eb1d285
to
624c379
Compare
@AparnaKarve, @michaelkro put up with me for 30 minutes and we have da solution, MORE DUPLICATE CODE EVERYWHERE aka, when you schedule or unschedule we refetch plans 😋 👍 i picked option 5, he picked option 3 |
@priley86 but @AparnaKarve is out today/tomorrow, can you confirm the desired behavior/merge? 🙇♀️ |
@AllenBW sure thing... will test it out now. |
yes - calling I am going to follow up w/ some schema validation checks later on... (always just a bonus). |
and it looks like ManageIQ/manageiq-api#400 needs to be backported before this PR... btw, it will really help if all dependencies are listed in the top description, as I could easily miss if it's in comment somewhere. |
[#369] Inactive migration plans can be scheduled to run (cherry picked from commit 18a306f) https://bugzilla.redhat.com/show_bug.cgi?id=1608351
Gaprindashvili backport details:
|
fixes #369
Where we're at...
this one's dedicated to @bdunne @gtanzillo @abellotti
https://bugzilla.redhat.com/show_bug.cgi?id=1564255