-
Notifications
You must be signed in to change notification settings - Fork 91
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
Created Lifecycle menu #912
Conversation
@Loicavenel Per your request, here is the change. Please let us know if that is what you had in mind. /cc @serenamarie125 for UX review. |
|
||
beforeEach(module('app.services','app.shared')); | ||
beforeEach( () => { | ||
bard.inject('VmsService', 'CollectionsApi'); | ||
bard.inject('VmsService', 'CollectionsApi', 'RBAC'); |
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.
Hmmm...are we checking the test files for StandardJS formatting? @AllenBW did we put that in to test in Travis? The ;
is not allowed by StandardJS
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.
We aren't checking test files @chriskacerguis
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.
he aint lying, we weren't before, wasn't going to add it in the conversion (https://github.com/ManageIQ/manageiq-ui-service/blob/master/package.json#L199-L200)
For posterity, the pt https://www.pivotaltracker.com/story/show/149777601 |
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.
@chriskacerguis @Loicavenel Wondering why we are prioritizing this effort while the whole page is being rewritten here why not just update the mock to include the change (which btw it doesn't presently) ?
@@ -130,7 +134,8 @@ export function VmsService (CollectionsApi, RBAC) { | |||
create: RBAC.hasAny(['vm_snapshot_add']), | |||
delete: RBAC.hasAny(['vm_snapshot_delete']), | |||
deleteAll: RBAC.hasAny(['vm_snapshot_delete_all']), | |||
revert: RBAC.hasAny(['vm_snapshot_revert']) | |||
revert: RBAC.hasAny(['vm_snapshot_revert']), | |||
instanceRetire: RBAC.hasAny(['instance_control', 'instance_retire']) |
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 was (am) guilty of this, making up names for rbac permissions...
It would be best to keep the name as close to the actualproduct feature as possible, so for this line instance_control: RBAC.hasAny(['instance_control')]
is preferred
Unsure where this requirement is from. Shouldn't all retirement options be available here @Loicavenel |
The addition of retirement here is great ! But here are my questions/ concerns: |
@serenamarie125 I think we should not offer "change the retirement date" as this is a service. |
@chalettu can you please rebase, so NSP goes green? |
@chalettu can you please rebase, so NSP goes green? |
@serenamarie125 thoughts on @Loicavenel 's thoughts? |
1 similar comment
@serenamarie125 thoughts on @Loicavenel 's thoughts? |
In discussing this feature with @Loicavenel we had concluded that only offering the option to retire the VM now should be the only available option at the VM level. @serenamarie125 I will change the wording in the popup to say VM instead of Resource. Will that work for updating the verbiage appropriately? |
@chriskacerguis, loic's comments were on the ability to change the retirement value. I'm fine with that. |
@chalettu As for the dialog, can you change:
|
@serenamarie125 this dialog pictured is not for a Service, its for a VM that is part of a service. I can go head and change the verbiage to add the term Retire but for all those places you mentioned using servicename, they don't fit this dialog as it is on the VM level. I will attach a screenshot of the updated look. |
@chalettu my bad, i edited my comments with VM name rather than Resource. Thank you! |
@serenamarie125 , here is a copy of the updated modal. Please let me know if we need to make any adjustments or if we can approve this PR . |
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.
Gonna apppprooooovvveeeeee but @chalettu @chriskacerguis where do we stand on standard in .spec.js ? imma thinking it should be turned on for consistency... (in another pr of course)
@AllenBW 👍 yeah, we should turn it on for the .spec.js |
Hey @chalettu, are you able to include the name of the VM rather than saying "this VM?" |
ba369d8
Checked commits https://github.com/chalettu/manageiq-ui-service/compare/ba7e0f3d5bc2f99f11e30c191946579e3ed999cc~...ba369d818bb8d2b8dc2c27d561520e6420cfacdf with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@serenamarie125 I was able to add the VM name to modal. Please let me know if you think it's good to go. |
@miq-bot add_label ux/approved |
@miq-bot remove_label ux/review |
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.
LGTM @chalettu . Thanks!
@Loicavenel could you please add your approval if you are good with this? |
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.
🤙 🇲🇰
@miq-bot add_label enhancement
@miq-bot add_label fine/no
@miq-bot add_label ux/review
@miq-bot add_label my services / details
Issue: #936