c9bfb763c2
Fixed action status_message update restrictions to allow updates when action is already in SKIPPED state. Previously, users could only update the status_message when initially transitioning to SKIPPED state. Changes include: - Modified validation logic to allow status_message updates for SKIPPED actions - Changed exception type from PatchError to Conflict for better semantics - Added comprehensive test coverage for the new behavior - Updated API documentation and samples - Added release note documenting the fix This enables administrators to fix typos, provide more detailed explanations, or expand on reasons in action status messages after the action has been skipped. Generated-By: claude-code Closes-Bug: #2121601 Change-Id: I64def708389a8ecd32080fba1638a4499ead349d Signed-off-by: Sean Mooney <work@seanmooney.info>
11 lines
555 B
YAML
11 lines
555 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixed action status_message update restrictions to allow updates when
|
|
action is in SKIPPED state. Previously, users could only update the
|
|
status_message when initially changing the action state to SKIPPED.
|
|
Now users can update the status_message field at any time while the
|
|
action remains in SKIPPED state, enabling them to fix typos, provide
|
|
more detailed explanations, or expand on reasons that were initially
|
|
omitted. For more details, see the bug report:
|
|
https://bugs.launchpad.net/watcher/+bug/2121601 |