Skip to content

Conversation

@zherman0
Copy link
Member

@zherman0 zherman0 commented Jul 2, 2019

Add a kebab with option of Remove Volume on all volumes in order to remove said volume from a resource.

This also entails a slight refactor for the VolumesTable component which currently takes a podTemplate but must now take a full resource so that I can remove the volumes from said resource.

Original:
volume-table-no-kebab

With Kebab:
volume-table-with-kebab

With Kebab Open:
volume-table-with-kebab-open

Confirmation Screen:
remove-volume-modal

@openshift-ci-robot openshift-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 2, 2019
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 2, 2019
@zherman0 zherman0 changed the title Remove volume feature Add: Remove volume feature Jul 2, 2019
@zherman0
Copy link
Member Author

zherman0 commented Jul 2, 2019

/assign @spadgett

@spadgett spadgett added this to the v4.2 milestone Jul 2, 2019
@zherman0 zherman0 force-pushed the remove-volume branch 3 times, most recently from a1266c9 to 276bb19 Compare July 6, 2019 00:55
@zherman0
Copy link
Member Author

zherman0 commented Jul 6, 2019

Refactored the VolumesTable component to use the PF tables which also made the new kebab handle resizing properly.

jul5-kebab

Small:
jul5-small

@zherman0
Copy link
Member Author

zherman0 commented Jul 9, 2019

/retest

@zherman0
Copy link
Member Author

zherman0 commented Jul 9, 2019

@spadgett - Can you please review this when you have time? Thanks.

@zherman0
Copy link
Member Author

zherman0 commented Jul 9, 2019

/test e2e-aws

@zherman0
Copy link
Member Author

@spadgett - Ready for review. Thanks.

@zherman0
Copy link
Member Author

/test e2e-aws

@zherman0
Copy link
Member Author

/retest

1 similar comment
@zherman0
Copy link
Member Author

/retest

Copy link
Member

@spadgett spadgett left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 18, 2019
@spadgett
Copy link
Member

/retest

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spadgett, zherman0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 18, 2019
@zherman0
Copy link
Member Author

/retest

@zherman0
Copy link
Member Author

/test e2e-aws

@zherman0
Copy link
Member Author

/retest

@zherman0
Copy link
Member Author

/test e2e-aws

@anmolsachan
Copy link
Contributor

anmolsachan commented Jul 19, 2019

I tested this PR locally

Screenshot from 2019-07-19 16-39-09

@zherman0 Is displaying the type of Volume not a part of this PR ? I see that in the initial screenshots

@zherman0
Copy link
Member Author

/test e2e-aws

Copy link
Contributor

@anmolsachan anmolsachan left a comment

Choose a reason for hiding this comment

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

@zherman0 I suppose following should be added to

to show the attached PVC name and type as well.

persistentVolumeClaim: {
    id: 'persistentVolumeClaim',
    label: 'Persistent Volume Claim',
    description: 'A Persistent Volume Claim is a request for Storage from a Persistent Volume',
  },

@zherman0
Copy link
Member Author

/retest

@zherman0
Copy link
Member Author

/test e2e-aws

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants