This repository has been archived by the owner on Jul 5, 2023. It is now read-only.
Adopt registry docs into terraform-website repo #1517
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…f423b7f08e8c33072ad2eccd6b The Registry is a web service whose behavior isn't directly tied to Terraform core's release cycle; therefore, its docs should be decoupled from that release cycle as well. This version of the content comes from Terraform commit 6a847df39202caf423b7f08e8c33072ad2eccd6b, which was the top of the master branch at the time of _this_ commit.
This was part of the work approved as TF-153; since we just adopted the post-TF-153 Registry docs from the Terraform repo, we should update the title now.
nfagerlund
requested review from
apparentlymart,
justincampbell and
aicarmic
|
This is great! Thank you so much. |
nfagerlund
added a commit
to hashicorp/terraform
that referenced
this pull request
Nov 18, 2020
The Registry is a web service whose behavior isn't directly tied to Terraform core's release cycle; therefore, its docs should be decoupled from that release cycle as well. hashicorp/terraform-website#1517 adopts the registry docs into hashicorp/terraform-website, which already hosts several other corpuses of documentation that aren't tied to Terraform core's version (like Terraform Cloud, Terraform Enterprise, and Extending Terraform). Once that PR is merged, we should remove the registry docs from this repository to avoid confusing anyone.
alisdair
approved these changes
Nov 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In recent months Terraform core has had a somewhat complicated branching and backporting strategy, which has had occasional bad effects on teams that need to maintain docs that have no real connection to Terraform core's release cadence. In particular, the Registry team has been hitting some "disappearing docs" issues due to the requirement to backport fixes to three different branches upon merge to main (
v0.13,v0.14, andstable-website).Well, the registry docs don't properly belong in the hashicorp/terraform repo in the first place; they were just there because terraform-website initially didn't have any real textual content when we first split the provider repos out. Now that we have a convention of maintaining docs for web services (Terraform Cloud) in this repo, we should do the same for the Registry.
After this PR is merged, we'll be free to delete the registry docs from the terraform repo itself.