chore: handle non-standard registries more automatically #854
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.
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.