Warn about using the opentofu/
namespace for HashiCorp providers
#1345
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.
As indicated in #1342 (comment), the duality of the
opentofu/
andhashicorp/
namespace is confusing and leads to problems. To avoid this footgun, the present PR adds warnings to the HashiCorp-mirrored providers in theopentofu/
namespace only.Unfortunately, this means that people who switched to the
opentofu/
namespace because they do not want to have HashiCorp mentioned in their configuration will now begin to see a warning. However, given that the maintainer of these providers is in fact HashiCorp, using theopentofu/
namespace is misleading anyway.