-
Notifications
You must be signed in to change notification settings - Fork 179
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
Provider-defined functions support #1674
Comments
Posting my findings about the earlydecoder output stuff that is causing The value itself is also stored in a map, but that one is never read. So, I don't think we can remove the handling there, but we can ignore |
Shipped 🎉 |
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. |
Background
Terraform will introduce provider-defined functions in an upcoming release. This will allow provider authors to ship their own functions. Practitioners will be able to use them in their Terraform configuration using a new function call syntax:
provider::aws::noop()
.We currently support all built-in core functions as static definitions in terraform-schema. The provider functions will be part of the provider schema JSON and should be parsed whenever we get a provider schema (bundled or via CLI). Both need to be merged into a single list of function signatures.
Expected User Experience
Syntax highlighting, completion, hover, semantic tokens, and signature help are working as expected for provider-defined functions.
Proposal
hcl
FunctionCallExpr
NameRange
for namespaced function call expressions hcl#650hcl-lang
nil
expressionsterraform-json
terraform-schema
terraform-ls
coreFunctions
with the new functions merger terraform-ls#1613 -> PRsyntax
Stretch Goals
The text was updated successfully, but these errors were encountered: