IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-30 10:47:14 -06:00
Code Issues Packages Projects Releases Wiki Activity
7ef92417d1
opentofu/website/docs/internals/archiving.html.md
Chris Doherty 71c79522c6 website: Add docs/internals/archiving.html to describe the archiving process. (#18831) 
Add docs/internals/archiving.html to describe the archiving process.
2018-09-10 17:32:43 -07:00

1.6 KiB
Raw Blame History

layout page_title sidebar_current description
docs Archiving Providers docs-internals Terraform is built on a plugin-based architecture, much of which is maintained by our user community. Occasionally, unmaintained providers may archived to reduce confusion for users and developers.

Archiving Providers

As contributors' circumstances change, development on a community-maintained Terraform provider can slow. When this happens, HashiCorp may use GitHub's "archiving" feature on the provider's repository, to clearly signal the provider's status to users.

What does archiving mean?

  1. The code repository and all commit, issue, and PR history will still be available.
  2. Existing released binaries will remain available on the releases site.
  3. Documentation for the provider will remain on the Terraform website.
  4. Issues and pull requests are not being monitored, merged, or added.
  5. No new releases will be published.
  6. Nightly acceptance tests may not be run.

HashiCorp may archive a provider when we or the community are not able to support it at a level consistent with our open source guidelines and community expectations.

Archiving is reversible. If anyone from the community is willing to maintain an archived provider, please reach out to the Terraform Provider Development Program at terraform-provider-dev@hashicorp.com.