Deletes with nargs should follow a consistent pattern
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | python-openstackclient |
Fix Released
|
Medium
|
Reedip | |
Bug Description
Deletes of resources with nargs should follow a consistent pattern where
* delete failures do not stop the delete of other resources
* a useful message gets printed for each failure
* $? should be non zero for partial failure
Similar to https:/
This should also include an updated to the developer docs which
documents the pattern for commands to follow.
| description: | updated |
| description: | updated |
| Changed in python-openstackclient: | |
| assignee: | nobody → Reedip (reedip-banerjee) |
| Richard Theis (rtheis) wrote : | #1 |
Fix proposed to branch: master
Review: https:/
| Changed in python-openstackclient: | |
| status: | New → In Progress |
Change abandoned by Steve Martinelli (<email address hidden>) on branch: master
Review: https:/
Reason: i believe this work is already finished
| Steve Martinelli (stevemar) wrote : | #4 |
Several of these have been implemented without referencing this bug. Let's take them on a case by case basis with new bugs.
| Changed in python-openstackclient: | |
| status: | In Progress → Fix Released |
| importance: | Undecided → Medium |
Another consideration is whether or not it should be considered a delete failure if the resource does not exist. The question was raised by Brad Behle here: https:/