Conventions for this repo's GitHub Actions workflows — pinning actions to full SHAs, updating action versions, the build/lint/generate/test/acceptance jobs, the companion meshfed-release merge order, and gotestsum coverage reporting. Use when editing .github/workflows/*.yml, bumping an action version, or debugging a CI job.
How to develop meshStack Terraform resources and data sources — the implementation, example .tf files, the testconfig builder, a good create→update→import TestAcc test (plancheck/statecheck, xknownvalue), and the cross-cutting schema/client design conventions (meshObject refs, DTOs, Id/Uuid naming, value receivers, list-query structs, preview API, computed-only outputs). Use when adding or reworking a resource/data source, writing its acceptance test, or applying the provider's schema/client conventions. Cites the cleanest existing examples to copy from.
Run and debug the meshStack provider acceptance tests (TF_ACC=1) against a local backend, including bringing that backend up. Use when asked to run acceptance tests, investigate acceptance-test failures, or correlate provider errors with backend behavior.
Maintain CHANGELOG.md and pick the next version for this provider. Use when adding a changelog entry for a PR, deciding the next version number, or preparing main to be tagged/released. Derives the anticipated version from commits since the last git tag. Key rule — no "Unreleased" section; the top section always carries the concrete anticipated next version, and main is always ready to tag.
Modern Go idioms used in this repo (Go 1.26) — the new(expression) builtin for inline pointers, the generics patterns the codebase relies on (typed clients, mock stores, variant unions, the generic TF value-conversion layer, map/iter helpers), and the go1.26 `go fix` modernizer pass. Use when writing or reviewing Go that creates pointers, defines type-parameterized helpers, touches generic.Set/Get, or running a modernization sweep.
Build and run a meshStack Terraform config in the git-ignored scratch/ dir against a meshStack you hold API credentials for (a local dev stack or a remote dev/sandbox), using the dev-built provider binary via dev_overrides. Use to reproduce or debug a provider bug or a failing acceptance test, OR to scaffold a demo / a working starting point for platform engineering — by dumping a test's HCL or hand-writing one.