feat(rules): allow patching of all rule fields #888
Conversation
|
/build_test |
|
Workflow started at 4/22/2025, 4:42:58 PM. View Actions Run. |
|
CI build and push: At least one test failed ❌ |
|
No GraphQL schema changes detected. |
|
No OpenAPI schema changes detected. |
|
/build_test |
|
Workflow started at 4/22/2025, 4:48:45 PM. View Actions Run. |
|
No OpenAPI schema changes detected. |
|
No GraphQL schema changes detected. |
|
CI build and push: At least one test failed ❌ |
|
CI build and push: All tests pass ✅ |
andrewazores
force-pushed
the
patch-rules
branch
from
026a07a to
6537c94
Compare
|
/build_test |
|
Workflow started at 4/23/2025, 3:05:36 PM. View Actions Run. |
|
No OpenAPI schema changes detected. |
|
No GraphQL schema changes detected. |
|
CI build and push: All tests pass ✅ |
Welcome to Cryostat! 👋
Before contributing, make sure you have:
mainbranch[chore, ci, docs, feat, fix, test]To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/mainRelated to cryostatio/cryostat-web#1581
Description of the change:
Allows more Automated Rule fields to be updated by the existing PATCH endpoint. Rule names cannot be modified this way but anything else can be.
Motivation for the change:
Required for upcoming frontend feature to allow editing existing Rules or duplicating Rules.
How to manually test: