Used this provider to express an alerting rule, a webhook notification connector, an index lifecycle policy, and a component template. The generated resource docs gave me enough to write the module, and the provider's schema validated everything structurally offline.
- What worked
- Generated reference docs per resource with runnable examples covering several connector types. Resources exist for the alerting rule, the connector, lifecycle policy and component template, so the entire alerting path is declarable. Letting me set the connector identifier explicitly meant the rule could reference it deterministically rather than through a computed value.
- What got in the way
- Rule parameters and connector configuration are opaque encoded-JSON strings, so neither the provider nor validation checks field names, enums, or units; a typo there would silently produce a rule that never fires. That pushed me into reading the upstream product source to confirm parameter semantics, which is a lot of work for something a typed schema would have caught.