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.

An error has occurred, https://github.com/hashicorp/cdktf-repository-manager/runs/6107550391.

Would be great to have a PR based workflow to drive upgrades in dependent repositories. Essentially, we can can take this workflow and trigger it based on relevant changed files in pull requests to open pull requests in dependent repos.

Effectively, all PR events would have to be mirrored to the dependent PRs.

Update issue title

• I have updated the title.

Provider URL

https://registry.terraform.io/providers/aiven/aiven

What type of provider is this?

Partner

Why do you need a pre-built package for this provider?

Why do you need a pre-built package for this provider?

A pre-built package for the Aiven Provider for Terraform is essential for our customers and their development processes, as well as reduction in build times.

What is your use case?

Our customers use the Aiven Provider for Terraform for various infrastructure management tasks, including:

• Managing a centralized infrastructure repository.
• Setting up Aiven clusters.
• Creating Aiven for Kafka topics and users for all projects and users.
• Abstracting Terraform provider bindings into a custom library for easier management.

Have you run into performance challenges that seem like they would be resolved with a pre-built provider? If so, what kind of stats are you seeing?

Yes, generating providers locally has led to performance challenges for our customers. Each build increases the overall build time, even if the process could be cached. This repetitive generation process is inefficient and time-consuming. By providing a pre-built package, the build times would be reduced significantly, enhancing overall productivity and efficiency.

Are you sure you need a pre-built provider?

• I am aware that I can already use this provider with CDKTF today by generating the bindings locally.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• Note that we cannot accept community/external PRs to create new prebuilt providers; these require a maintainer to submit the PR

Update issue title

• I have updated the title.

Provider URL

https://registry.terraform.io/providers/SumoLogic/sumologic

What type of provider is this?

Partner

Why do you need a pre-built package for this provider?

I would like to have Maven/Java package built for the provider for convenience of the users.

Admittedly I haven't run into any performance challenges, it's just the rebuilding the CDKTF bindings with every CI run seems like a wasted effort.

I am not fully sure if this use-case falls into the usage of cdktf-repository-manager.

Are you sure you need a pre-built provider?

• I am aware that I can already use this provider with CDKTF today by generating the bindings locally.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• Note that we cannot accept community/external PRs to create new prebuilt providers; these require a maintainer to submit the PR