github-actions[bot]
commented
1 week ago Thanks for the feature request. We evaluate it and update the issue accordingly.
Community Note
Voting for Prioritization
- Please vote on this issue by adding a 👍 reaction to the original post to help the community and 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.
Volunteering to Work on This Issue
- If you are interested in working on this issue, please leave a comment.
- If this would be your first contribution, please review the contribution guide.
lechnerc77
What area do you want to see improved?
terraform provider
Is your feature request related to a problem? Please describe.
As part of our cooperation we use the terraform-provider-btp to power our crossplane based btp provider, which allows for continuous resource reconcilation. The technology being used here is based on upjet.
In previous releases upjet is using a forked terraform process to leverage the providers CRUD functionality. In favor or performance and lowered resource consumption they now offer a more lightweight integration, in which the providers code can be run without involving a terraform process (see upjets release and relevant PR).
This new approach is a lot faster and consumes less memory, so we highly anticipate using the btp terraform provider in that way.
Describe the solution you would like
To leverage this approach the provider needs to be exposed, so that it can be used from the outside. Here is an example of how that has been done for the aws terraform provider: https://github.com/upbound/terraform-provider-aws/blob/upjet-v5.31.0/xpprovider/xpprovider.go#L30.
Describe alternatives you have considered
No response
Additional context
Since implementing that is probably done best with trying its import into the crossplane provider I offer my/our help with contributing this feature set.