terraform-provider-mongodbatlas

Best practices for writing and organizing acceptance tests in this Terraform provider. Use when creating new acceptance tests, modifying existing tests, fixing flaky tests, or reviewing test code. Covers test consolidation, avoiding duplicates, plural data source ordering, and plan-only validation tests.

End-to-end workflow for supporting a new attribute in an autogenerated (serviceapi) resource or data source. Use whenever the Atlas API spec adds a field to an autogen resource — typically surfaced by the "Updates auto-generated production resources (DO NOT MERGE)" bot PR — or when asked to incorporate such a change, add a new attribute to a serviceapi resource, or follow up on an autogen visibility PR. Covers codegen config overrides, regeneration, acceptance tests, docs, and changelog.

Summarize a GitHub Actions test suite run for the mongodb/terraform-provider-mongodbatlas repo — fetches job logs, classifies failures, and produces a Slack summary led by an explicit code-regression verdict. Use when the user shares a workflow run URL or run_id, or when triggered by the test-suite webhook to decide whether on-call should investigate.

Standards for pull requests, documentation, and code review in this Terraform provider. Use when creating PRs, writing or editing documentation (schema descriptions, docs markdown, examples), reviewing code, or adding changelog entries. Covers PR structure, docs style guide, example conventions, and changelog practices.

Best practices for developing Terraform resources and data sources in this provider. Use when creating new resources, modifying schema definitions, implementing CRUD operations, handling state transitions, or working with autogenerated resources.