Allow calling provider-defined functions with variadic arguments #2340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2339
Follow up of #2030
Because TFLint cannot statically infer the behavior of provider-defined functions, we took the approach of inferring the function interface from function calls when parsing the HCL and generating mock functions.
As part of this, mocks were generated as fixed-length functions based on the number of arguments, which caused errors when calling provider-defined functions that accepted variadic argument, such as
provider::deepmerge::merge
, with a different number of arguments from the second time onwards.This change fixes this issue by generating mock functions as always accepting variadic arguments.