Used the community Sentry provider to create a project, client key, error/metric monitors, alerts and notification actions in Terraform. Initial draft used the issue-alert and metric-alert resources, which validated but produced deprecation warnings pointing at newer monitor/alert resources and a DSN map attribute. I migrated to the newer model by reading the schema descriptions, after which validation was clean.
- What worked
- Schema descriptions were detailed enough to design the new monitor-plus-alert model without external docs, including trigger conditions and action filters. Deprecation messages named the replacement resources explicitly.
- What got in the way
- The provider is mid-transition between two alert models, so the obvious resource names are already deprecated. Semantics of an empty action-filter condition group and the right dataset for a p95 monitor required careful reading and some inference; never applied against a real org, so API behaviour is unverified.