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
feat(terraform-provider): Add secondary release repo #6513
feat(terraform-provider): Add secondary release repo #6513
Conversation
Hi @secustor, can you refactor this a little before we focus on tests?
e.g. the logic becomes
|
6e580c9
to
961fdaf
Compare
961fdaf
to
c4582ff
Compare
Rebased and updated to the new mocking setup. Seems like the second nock scope is breaking the other unit tests. |
@secustor I fixed a couple of mocks you were missing. With the fallback logic you implemented, we need to mock both possible requests. |
@secustor are there any cases where results could be found in both registries and we'd prefer to combine results? |
@JamieMagee Thx for your support. @rarkins Not really the secondary repo contains only the available version and cpu architectures for the providers. |
Can you check out the recent commit I made which adds the concept registryStrategy = ‘hunt’? It simplifies the datasource implementations by pushing some logic into the index dispatcher. Let me know if you’re interested to refactor as part of this PR or you don’t mind me refactoring it after. |
This pull request introduces 2 alerts when merging d8dfea2 into 7e51c90 - view on LGTM.com new alerts:
|
This pull request introduces 2 alerts when merging cdf1516 into 7e51c90 - view on LGTM.com new alerts:
|
@rarkins I have refactored the changes to this new strategy system. |
🎉 This PR is included in version 21.14.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This PR adds
releases.hashicorp.com
as secondary repo for builds.The primary source is still
registry.terraform.io
as it has more meta information e.g. source code repositories, changelogs, ...Closes #5065