Acknowledgements
Describe the bug
manually calling PUT api/v1/incidents/incident-alerts makes new alerts added on that request dissapear, and be no tenant scoped
Regression Issue
Expected Behavior
calling the update must upsert the linked alerts, not remove them from the tenant and leave it alert less
Current Behavior
calling that put request (MANUALLY as it is not used on the frontend client, only mcp client) make newly added alerts just be not linted after the update
Reproduction Steps
- call PUT api/v1/incidents/incident-alerts adding new alerts to the link
- call GET api/v1/incidents/incident-alerts and check new alerts arent there
Possible Solution
No response
Additional Information/Context
No response
UTMStack Version
v12.0.0
Operating System and version
Hypervisor and Version | Server Vendor and Model
Browser and version
Acknowledgements
Describe the bug
manually calling PUT api/v1/incidents/incident-alerts makes new alerts added on that request dissapear, and be no tenant scoped
Regression Issue
Expected Behavior
calling the update must upsert the linked alerts, not remove them from the tenant and leave it alert less
Current Behavior
calling that put request (MANUALLY as it is not used on the frontend client, only mcp client) make newly added alerts just be not linted after the update
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
UTMStack Version
v12.0.0
Operating System and version
Hypervisor and Version | Server Vendor and Model
Browser and version