Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn about using the opentofu/ namespace for HashiCorp providers #1345

Merged
merged 4 commits into from
Dec 3, 2024

Conversation

abstractionfactory
Copy link
Contributor

@abstractionfactory abstractionfactory commented Dec 2, 2024

As indicated in #1342 (comment), the duality of the opentofu/ and hashicorp/ namespace is confusing and leads to problems. To avoid this footgun, the present PR adds warnings to the HashiCorp-mirrored providers in the opentofu/ 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 the opentofu/ namespace is misleading anyway.

Signed-off-by: AbstractionFactory <[email protected]>
Signed-off-by: AbstractionFactory <[email protected]>
Signed-off-by: AbstractionFactory <[email protected]>
@abstractionfactory abstractionfactory changed the title Warn about using the opentofu/ namespace for HashiCorp providers Warn about using the opentofu/ namespace for HashiCorp providers Dec 2, 2024
@abstractionfactory abstractionfactory marked this pull request as draft December 2, 2024 08:17
@abstractionfactory abstractionfactory marked this pull request as ready for review December 3, 2024 16:37
@abstractionfactory abstractionfactory merged commit a460f33 into main Dec 3, 2024
2 checks passed
@abstractionfactory abstractionfactory deleted the warn-opentofu-namespace branch December 3, 2024 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provider opentofu/aws ignores configuration block, leading to instance profile being used
4 participants