Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Expose Terraform Plugin Framework Provider #807

Closed
sdischer-sap opened this issue May 8, 2024 · 2 comments
Closed

[FEATURE] Expose Terraform Plugin Framework Provider #807

sdischer-sap opened this issue May 8, 2024 · 2 comments
Labels
out-of-scope Out-of-scope; won't be worked on wontfix This will not be worked on

Comments

@sdischer-sap
Copy link
Member

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.

@sdischer-sap sdischer-sap added enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion. labels May 8, 2024
Copy link

github-actions bot commented May 8, 2024

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
Copy link
Member

The feature is not implemented by any official Terraform provider. It adds no value for customers using the provider in their Terraform setup.

If you want to use the mentioned new upjet functionality and leverage the provider for the bridge implementation, please use the same mechanics as mentioned in the references, namely forking the provider and adding the change in the fork

@lechnerc77 lechnerc77 added wontfix This will not be worked on out-of-scope Out-of-scope; won't be worked on and removed enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion. labels May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
out-of-scope Out-of-scope; won't be worked on wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants