The Archestra Terraform provider lets you manage Archestra resources — agents, MCP servers, identity providers, teams, LLM keys, security policies, organization settings — as code.
- Registry: https://registry.terraform.io/providers/archestra-ai/archestra/latest
- Guides: Getting Started · Authentication · Resource Bring-up Order · BYOS Vault · Common Issues
- Schema reference: docs/ (auto-generated)
- Per-resource snippets: examples/resources/ — illustrative HCL for every resource
- Runnable examples: examples/basic/ (smallest end-to-end chain) · examples/complete/ (full bring-up wired together)
- Changelog: CHANGELOG.md — read before widening a version constraint
- Contributing: CONTRIBUTING.md
terraform {
required_providers {
archestra = {
source = "archestra-ai/archestra"
version = "~> 0.6.0"
}
}
}
provider "archestra" {
# base_url + api_key are read from ARCHESTRA_BASE_URL / ARCHESTRA_API_KEY.
}export ARCHESTRA_BASE_URL="https://archestra.your-company.example"
export ARCHESTRA_API_KEY="arch_..." # mint via Settings → API Keys
terraform init && terraform applyFull walkthrough in the Getting Started guide.
make build # build the provider binary
make install # build + install into $GOPATH/bin (for dev_overrides)
make test # unit tests + drift checks
make testacc # acceptance tests against $ARCHESTRA_BASE_URL
make generate # regenerate docs/ from schema + examples
make lint # golangci-lint v2Prerequisites, dev_overrides setup, the merge-patch + AttrSpec
architecture, drift-check tests, the new-resource checklist, and the
acceptance-test env gates (ARCHESTRA_READONLY_VAULT_ENABLED,
ARCHESTRA_TEST_IDP_ID) live in CONTRIBUTING.md.
Automated via GitHub Actions using
release-please —
conventional-commit messages drive version bumps and
CHANGELOG.md entries.