Upgrade the TFE prebuilt provider to v0.31.0 (or upgrade to v0.32.0 when released)
nikolay opened this issue · comments
The version you're anchored to (v0.26.1) is almost a year old! The choice to use CDKTF should not come with a major compromise and require a downgrade in production and refactoring states (in this case, importing resources against older versions). TFE is used by paying customers who should get a better experience, I believe! Those using older versions in production can always use an older version of the prebuilt provider.
As a side note, I saw you upgraded azurerm to a major version bump, but your CDK prebuild provider was just a patch build. I realize the challenges with complex compound versions in SemVer, but at least when the provider is upgraded to a major new version, the CDKTF prebuild provider's version should also have a major bump.
I agree, we should be updating the providers on a more regular basis. We are working on an automated solution, but it's going to take some time. In the mean time if you'd like to help you can update outdated providers here.
About the update of azurerm, this is a bit tricky since technically a major version bump on a initial development version is done by updating the minor version. The tooling did just that and warned about breaking changes in the release. I can understand that this is confusing though, so I'll see if we can upgrade all < 1.0 packages to a 1.0 with the next release. In the meantime I suggest you pin packages to their major and minor version, at least the ones that have a 0 as major version.
@DanielMSchmidt I submitted a PR to use the proper variable set support, which is only available in v0.33 (the earlier versions use now deprecated way to configure which workspaces use which sets). Please, review: #77
The new version is released, closing this
I'm going to lock this issue because it has been closed for at least 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems similar to this, please open a new issue so we can investigate further.