You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can you update the required_providers in all of your modules to at least be >=? The ~> version specification is making it very hard to manage dependencies when using your modules.
Expected Behavior
To not get Error: Failed to query available provider packages errors
Use Case
When trying to use Cloudposse modules and somewhat recent versions of official providers, like hashicorp/aws and hashicorp/github, there are a lot of dependency version conflicts.
Describe Ideal Solution
We should always be able to use later versions of providers with Cloudposse modules and not be pinned to old major versions. Also this current paradigm seems difficult to maintain.
Alternatives Considered
Maybe one option is to have tags for each module where dependencies are pinned to specific versions. Though that would also be very high maintenance.
Additional Context
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider
hashicorp/github: no available releases match the given constraints >= 3.1.*,
>= 3.1.*, >= 3.1.*, ~> 2.8.0
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider
hashicorp/random: no available releases match the given constraints >= 3.0.*,
~> 2.*, ~> 2.1, ~> 2.1, ~> 2.1
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider
hashicorp/local: no available releases match the given constraints >= 2.0.*,
~> 1.3, ~> 1.2, ~> 1.2, ~> 1.2, >= 1.2.*, ~> 1.2, >= 1.2.*, ~> 1.*, ~> 1.3, ~>
1.2, ~> 1.2, >= 2.0.*, ~> 1.2, >= 2.0.*, ~> 1.3, ~> 1.2, ~> 1.2, ~> 1.2, ~>
1.3, ~> 1.2, ~> 1.2, ~> 1.3, ~> 1.2, ~> 1.2, ~> 1.2, ~> 1.3, ~> 1.2, >= 1.2.*,
~> 1.2
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/aws:
no available releases match the given constraints >= 2.42.*, ~> 2.0, ~> 2.0,
~> 2.0, >= 3.0.*, >= 2.0.*, >= 2.0.*, >= 2.67.*, < 4.0.*, ~> 2.0, ~> 2.0, ~>
2.0, >= 2.42.*, ~> 2.0, >= 2.42.*, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.42, >= 2.34.*,
< 4.0.*, ~> 2.42, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.42, ~> 2.0, >= 2.0.*, >= 2.0.*,
~> 2.0, ~> 2.0
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider hashicorp/null:
no available releases match the given constraints >= 3.0.*, ~> 2.0, ~> 2.0, ~>
2.0, >= 2.0.*, ~> 2.0, >= 2.0.*, ~> 2.*, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~>
2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0, ~> 2.0,
>= 2.0.*, ~> 2.0
The text was updated successfully, but these errors were encountered:
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature
Can you update the
required_providers
in all of your modules to at least be>=
? The~>
version specification is making it very hard to manage dependencies when using your modules.Expected Behavior
To not get
Error: Failed to query available provider packages
errorsUse Case
When trying to use Cloudposse modules and somewhat recent versions of official providers, like
hashicorp/aws
andhashicorp/github
, there are a lot of dependency version conflicts.Describe Ideal Solution
We should always be able to use later versions of providers with Cloudposse modules and not be pinned to old major versions. Also this current paradigm seems difficult to maintain.
Alternatives Considered
Maybe one option is to have tags for each module where dependencies are pinned to specific versions. Though that would also be very high maintenance.
Additional Context
The text was updated successfully, but these errors were encountered: