alarm-rule-templates
Copy templates for alarm rules.
List rule templates
Returns the rule templates of the tenant. Templates are tenant-local: there is no centrally delivered set, and a template is only ever copied.
Create a rule template
Stores a new template. Its condition is checked the same way a rule's is - a template whose CEL does not compile would only produce rules that cannot run, and finding that out at the first tick of the first rule made from it would be the worst moment. Responds 400 in that case.
Get a rule template
Returns one rule template with its condition, parameter defaults and texts - the copy a rule is created from. A template has no relation to the rules made from it (RG-3), so the answer says nothing about whether it has been used.
Update a rule template
Replaces the template. This does NOT touch rules that were created from it - a template is a copy template, not a running reference, and there is no path along which a change could reach them.
Delete a rule template
Deletes the template. Rules created from it are unaffected and keep working - they carry no reference to it.
Create a rule from a template
Copies the fields of the template into a new rule and stores it. The new rule is **unbound and disabled**: which objects it watches is exactly what a template cannot know, and an enabled rule without a binding would tick and evaluate nothing, which looks like a working rule and is not one. Bind it and enable it through the rule endpoints afterwards.