-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Extend plugin protocol to allow providers to define custom terraform functions #25940
Comments
HI @iwarapter ! Thank you for opening this feature request - it's an interesting idea! Can you give some examples of your use-case? I would think that any function that would be useful for a single provider would be something we would want to enable for all users, so I'm very curious to hear what kind of provider-specific functions you are thinking of! |
Hi @mildwonkey, sorry for the extremely late reply 😂 . I was originally looking for support for more crypto specific functions, such as RSA/EC to JWKS transformation. However I think this (specific) use-case might actually be best suited in terraform. I have raised #30419 to track this and #30420 as a draft implementation. Thanks! |
Hi @iwarapter! As I mentioned over in #30419, I'm going to close this in favor of the existing #2771, just to consolidate the discussion. I'm sorry we didn't notice this was a duplicate when you originally opened it. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Use-cases
Providers could supply additional helper functions to make using their resources more easy, instead of using local-exec or other hacks for functionality not provided by the core terraform functions.
Proposal
Allow providers to expose terraform functions
https://www.terraform.io/docs/configuration/functions.html
References
https://discuss.hashicorp.com/t/extendable-terraform-functions/13023
The text was updated successfully, but these errors were encountered: