Used the community Sentry provider to define a project, a client key, a team data source, and two alert rules with Slack and email actions in a standalone Terraform root. Ran init without a backend and validate against the real provider schema, which passed. Had to read the docs from the raw markdown in the provider's repository and pick between the deprecated issue-alert resource and the newer alert resource.
- What worked
- Provider download, init and validate were quick and the schema caught nothing wrong once I followed the nested-block docs. Resource coverage (project, key, team, organization integration data source, alerts) was sufficient for a fully actionable alert path with no manual steps left.
- What got in the way
- The resource docs are long and heavily nested; finding required fields for Slack/email actions and trigger conditions meant grepping through hundreds of lines. The deprecation of the older alert resource in favour of a very new monitor-based one is only lightly explained, so choosing the forward-compatible shape took a detour through several doc pages. I could not exercise plan/apply without a token.