Skip to content

Conversation

jacobbednarz
Copy link
Contributor

When everyone was upset with Hashicorp and creating their own registries, it was the wild west and we didn't really have a great way to universally detect the registry in use without it being explicitly provided.

Fast forward to today, everyone* now ships this as part of their state implementation (like Hashicorp always did) so it's easier to determine the registry once it is initialised.

* Well, anyone that has a > 0.01% footprint for usage.

When everyone was upset with Hashicorp and creating their own
registries, it was the wild west and we didn't really have a great way
to universally detect the registry in use without it being explicitly
provided.

Fast forward to today, everyone* now ships this as part of their state
implementation (like Hashicorp always did) so it's easier to determine
the registry once it is initialised.

_* Well, anyone that has a > 0.01% footprint for usage._
@vaishakdinesh vaishakdinesh self-assigned this Mar 27, 2025
@jacobbednarz jacobbednarz merged commit 557b3ee into master Mar 27, 2025
7 checks passed
@jacobbednarz jacobbednarz deleted the handle-custom-registries-based-on-state-file branch March 27, 2025 22:24
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.

2 participants