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

Delete Transformation Mappings feature #356

Merged
merged 10 commits into from
May 31, 2018

Conversation

AparnaKarve
Copy link
Contributor

@AparnaKarve AparnaKarve commented May 30, 2018

Added support for deleting transformation mappings


pf delete icon added in the actions area in the list
(shows disabled and enabled delete icons)
screen shot 2018-05-29 at 7 13 04 pm


Simple delete confirmation dialog for a mapping -
screen shot 2018-05-29 at 7 13 35 pm


Delete confirmation dialog that shows associated Plans that are not started and/or
associated plans in error -
screen shot 2018-05-29 at 7 13 54 pm


Fixes #297

@AparnaKarve
Copy link
Contributor Author

@vconzola The second Delete Confirmation modal above shows the affected Plans.

Do you think we should also delete these Plans -- since there is no point in keeping the plans around without their transformation mapping?

/>
<Modal
Copy link
Member

Choose a reason for hiding this comment

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

would you mind moving this Modal to another stateless functional component? i.e. components/DeleteMappingConfirmationModal ? I think extracting this Modal JSX and relevant logic there in another component would be nice...

Will try to test this out on my side today...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Created a new stateless functional component - DeleteInfrastructureMappingConfirmationModal and moved all the related logic there that is required to construct the delete message.

@vconzola
Copy link

@AparnaKarve We need to keep the plans so users can go back and see which VMs have been migrated. If users want to then archive the plans they can do that separately. That's the direction I've gotten from Brett and Marco. Your question does bring up an interesting point, however. We need to decide what to display for plans that no longer have an associated mapping. I'll create an issue for this.

@himdel
Copy link
Contributor

himdel commented May 30, 2018

(Depends on ManageIQ/manageiq-api#383 (in case this goes to gaprindashvili))

call the component from `InfrastructureMappingsList`
<Icon type="pf" name="add-circle-o" />
&nbsp;{__('Create Infrastructure Mapping')}
</a>
<div>
Copy link
Member

@priley86 priley86 May 31, 2018

Choose a reason for hiding this comment

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

i think we can just use React.Fragment instead of introducing the additional div ? i.e. just wrap Grid.Col and DeleteInfrastructureMappingConfirmationModal w/ React.Fragment

@priley86
Copy link
Member

thanks for the updates @AparnaKarve ! looks good...just one other minor nit...

@himdel looks like this API was merged... i will update locally and test this first thing tomorrow.

@priley86
Copy link
Member

confirmed this works locally. merging.

@priley86 priley86 merged commit a417e6a into ManageIQ:master May 31, 2018
@AparnaKarve AparnaKarve deleted the delete_transformatin_mappings branch May 31, 2018 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants