bulk enable/disable endpoint
Bug #1668529 reported by
yxu
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Aodh |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
In current version of aodh , alarm's atrribute 'enable' is just a boolean value .
Could we make it an object , for when I want to disable a bunch of alarm, I have to update a lot alarms to set every one of them .
just like this :
create an alarm shield : post to /v2/shield
delete an alarm shield : delete /v2/shield/
...
If 'enable' is an object , just change one place . In my work environment , that is more efficient .
| information type: | Public → Public Security |
| information type: | Public Security → Public |
Revision history for this message
| gordon chung (chungg) wrote | #1 |
| summary: |
- could we design alarm disable/enable as an object? + bulk enable/disable endpoint |
| Changed in aodh: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
seems you want a bulk enable/disable endpoint?