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
we have moduleA which use provider version 1.x, and we have a new moduleB using provider 2.x. Now, due to the limitation of the provider versioning, we will have to upgrade the moduleA to use provider version 2.x. We're not able to use both version of providers at the same time even with different aliases
Attempted Solutions
nil
Proposal
#16641
This support was not added due to reasons mentioned in the above issue. Just wanted to checkin and ask if anything changed in the architecture that we can add support multiple versions of same providers?
References
No response
The text was updated successfully, but these errors were encountered:
Hi @iamunni, there are no updates. This issue is somewhat related to #19932, in the sense that they both represent desired changes to the current restrictions in defining dependencies.
Terraform Version
Use Cases
we have moduleA which use provider version 1.x, and we have a new moduleB using provider 2.x. Now, due to the limitation of the provider versioning, we will have to upgrade the moduleA to use provider version 2.x. We're not able to use both version of providers at the same time even with different aliases
Attempted Solutions
nil
Proposal
#16641
This support was not added due to reasons mentioned in the above issue. Just wanted to checkin and ask if anything changed in the architecture that we can add support multiple versions of same providers?
References
No response
The text was updated successfully, but these errors were encountered: