-
Notifications
You must be signed in to change notification settings - Fork 90
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
ovirt_remove_stale_lun: Allow user to remove multiple LUNs #357
Conversation
Hello contributor, thanks for submitting a PR for this project! I am the bot who triggers "standard-CI" builds for this project. In order to allow automated tests to run, please ask one of the project maintainers to review the code and then do one of the following:
|
ci add to whitelist |
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.
Please add changelog
Currently, if a user has to remove multiple LUNs, they have to run the playbook individually for each LUNs. This is not that user friendly if the user has to remove many LUNs. This commit provides option to pass multiple LUNs.
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 now
Currently, if a user has to remove multiple LUNs, they have to run the playbook individually for each LUNs. This is not that user friendly if the user has to remove many LUNs. This commit provides option to pass multiple LUNs.
Currently, if a user has to remove multiple LUNs, they have to run the playbook individually for each LUNs. This is not that user friendly if the user has to remove many LUNs. This commit provides option to pass multiple LUNs.
Currently, if a user has to remove multiple LUNs, they have to run
the playbook individually for each LUNs. This is not that user
friendly if the user has to remove many LUNs. This commit provides
option to pass multiple LUNs.