Skip to content

docs: update Terraform registry publishing process to use HCP Terraform via core team#2623

Merged
jaredfholgate merged 6 commits intomainfrom
docs/tf-registry-publishing-update
Mar 9, 2026
Merged

docs: update Terraform registry publishing process to use HCP Terraform via core team#2623
jaredfholgate merged 6 commits intomainfrom
docs/tf-registry-publishing-update

Conversation

@jaredfholgate
Copy link
Member

Summary

This PR updates the documentation to reflect the new Terraform registry publishing process, which is now managed by the AVM core team via HCP Terraform.

Changes

owner-contribution-flow.md

  • Removed self-service publishing steps (sign in to HashiCorp Registry, publish manually)
  • Added instruction to contact the AVM core team for publishing
  • Clarified that subsequent versions are auto-published via HCP Terraform
  • Added explicit requirement that tags must include the \�\ prefix (e.g., \�0.1.0, not \

…rm via core team

- Publishing is now managed by the AVM core team via HCP Terraform
- Module owners should contact the core team instead of self-publishing
- Updated RACI table to reflect core team responsibility
- Clarified that tags must include the v prefix (e.g., v0.1.0)
@jaredfholgate jaredfholgate requested a review from a team as a code owner March 9, 2026 12:47
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 Maintainers need to triage still label Mar 9, 2026
@microsoft-github-policy-service

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

@jaredfholgate jaredfholgate self-assigned this Mar 9, 2026
- Merge external contributor and module owner flows into single page with tabs
- Remove nested terraform-contribution-flow folder
- Move testing content into contribution flow
- Create Advanced Topics & FAQ page for edge cases
- Move repository creation process to standalone page
- Remove service principal guidance, advocate az login
- Add terraform test support, remove Go test references
- Simplify prerequisites
- Update mermaid flow diagram to 9-step process
- Fix menu ordering to match _index.md
- Fix broken step reference in Fork section (step 1 -> step 2)
- Remove duplicate push instructions from Raise PR step
- Add explicit failure path for external contributor e2e tests
- Consolidate duplicate notice boxes in composition page
- Remove dangling cross-reference to deleted composition section
jaredfholgate and others added 2 commits March 9, 2026 16:46
Co-authored-by: Matt White <16320656+matt-FFFFFF@users.noreply.github.com>
Co-authored-by: Matt White <16320656+matt-FFFFFF@users.noreply.github.com>
@jaredfholgate jaredfholgate merged commit 9deb676 into main Mar 9, 2026
7 checks passed
@jaredfholgate jaredfholgate deleted the docs/tf-registry-publishing-update branch March 9, 2026 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs: Triage 🔍 Maintainers need to triage still

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants