Skip to content
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

Merged
merged 3 commits into from
Sep 28, 2017
Merged

Created Lifecycle menu #912

merged 3 commits into from
Sep 28, 2017

Conversation

chalettu
Copy link
Contributor

@chalettu chalettu commented Sep 6, 2017

@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

@chalettu
Copy link
Contributor Author

chalettu commented Sep 6, 2017

retire resource
Screenshot of implementation

@chriskacerguis chriskacerguis self-assigned this Sep 6, 2017
@chriskacerguis chriskacerguis added this to the Sprint 69 Ending Sep 18, 2017 milestone Sep 6, 2017
@chriskacerguis
Copy link
Contributor

@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');
Copy link
Contributor

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

Copy link
Contributor Author

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

Copy link
Member

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)

@AllenBW
Copy link
Member

AllenBW commented Sep 6, 2017

For posterity, the pt https://www.pivotaltracker.com/story/show/149777601

AllenBW
AllenBW previously approved these changes Sep 6, 2017
Copy link
Member

@AllenBW AllenBW left a 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'])
Copy link
Member

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

@serenamarie125
Copy link

Unsure where this requirement is from. Shouldn't all retirement options be available here @Loicavenel

@serenamarie125
Copy link

The addition of retirement here is great ! But here are my questions/ concerns:
1 - this option should only be available for VMs
2 - the menu itself shouldn't reference "resources"
3 - can we also add options to change the retirement date? I'm currently at the airport and don't have time to get onto the Ops UI to see the options, but i'm guessing that we should be able to sy either Retire now or Change retirement date
@Loicavenel curious on your thoughts
@chalettu i can provide better wording tonight/tomorrow if needed

@Loicavenel
Copy link

@serenamarie125 I think we should not offer "change the retirement date" as this is a service.

@chriskacerguis
Copy link
Contributor

@chalettu can you please rebase, so NSP goes green?

@chriskacerguis
Copy link
Contributor

@chalettu can you please rebase, so NSP goes green?

@chriskacerguis
Copy link
Contributor

@chalettu ^

@chriskacerguis
Copy link
Contributor

@serenamarie125 thoughts on @Loicavenel 's thoughts?

1 similar comment
@chriskacerguis
Copy link
Contributor

@serenamarie125 thoughts on @Loicavenel 's thoughts?

@chalettu
Copy link
Contributor Author

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?

@serenamarie125
Copy link

@chriskacerguis, loic's comments were on the ability to change the retirement value. I'm fine with that.

@serenamarie125
Copy link

serenamarie125 commented Sep 19, 2017

@chalettu As for the dialog, can you change:

  1. Dialog title to "Retire" (EVEN better if you can say "Retire - VM name")
  2. Action button to "Retire"
  3. Descriptive text to say "Are you sure you want to retire this service now?" (EVEN better if you can say "Are you sure you want to retire VM name now?")

@chalettu
Copy link
Contributor Author

@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.

@serenamarie125
Copy link

@chalettu my bad, i edited my comments with VM name rather than Resource. Thank you!

@chalettu
Copy link
Contributor Author

retire_modal @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 .

@chriskacerguis chriskacerguis removed this from the Sprint 69 Ending Sep 18, 2017 milestone Sep 25, 2017
chriskacerguis
chriskacerguis previously approved these changes Sep 25, 2017
AllenBW
AllenBW previously approved these changes Sep 25, 2017
Copy link
Member

@AllenBW AllenBW left a 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)

@chriskacerguis
Copy link
Contributor

@AllenBW 👍 yeah, we should turn it on for the .spec.js

@chriskacerguis chriskacerguis mentioned this pull request Sep 25, 2017
6 tasks
@serenamarie125
Copy link

Hey @chalettu, are you able to include the name of the VM rather than saying "this VM?"

@chriskacerguis chriskacerguis changed the title [Finishes #149777601] Created Lifecycle menu Created Lifecycle menu Sep 26, 2017
@miq-bot
Copy link
Member

miq-bot commented Sep 27, 2017

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
0 files checked, 0 offenses detected
Everything looks fine. 🏆

@chalettu
Copy link
Contributor Author

lifecycle @serenamarie125 I was able to add the VM name to modal. Please let me know if you think it's good to go.

@serenamarie125
Copy link

@miq-bot add_label ux/approved

@serenamarie125
Copy link

@miq-bot remove_label ux/review

Copy link

@serenamarie125 serenamarie125 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM @chalettu . Thanks!

@chriskacerguis
Copy link
Contributor

@Loicavenel could you please add your approval if you are good with this?

Copy link
Member

@AllenBW AllenBW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤙 🇲🇰

@chriskacerguis chriskacerguis removed the request for review from Loicavenel September 28, 2017 12:15
@chriskacerguis chriskacerguis added this to the Sprint 70 Ending Oct 2, 2017 milestone Sep 28, 2017
@chriskacerguis chriskacerguis merged commit 80724bb into ManageIQ:master Sep 28, 2017
@chalettu chalettu deleted the retire-vm-details branch January 10, 2018 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants