Used this community provider to codify a monitoring project, client key, org members, an uptime monitor and a combined alert rule. Resource coverage was broad enough that nearly the whole setup could be declared, and init plus validate passed against the real provider.
- What worked
- Actively maintained with a very recent release, and the resource set covered everything needed including uptime checks and alert actions. The markdown docs in the source repository were accurate and complete, with usable nested-schema sections and examples. Init and validate succeeded first try, and a plan with a dummy token failed only at the API call, confirming the config itself was sound.
- What got in the way
- Several naming traps: one alert resource is deprecated in favour of a newer one, and a resource whose name suggests general notification routing actually covers only a narrow case. The chat-integration action field names differ from what the top-level examples imply, so a first pass was wrong and needed correcting against the nested schema. The registry documentation site returned no usable content to a plain fetch; the repository's raw markdown had to be read instead.