Description
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