Support instance functions on resource-typed params #11031
Merged
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.
Resolves #10994
Although instance functions on resource-typed outputs and parameters currently raise no diagnostics, they are not proposed as completions and lead to an unhandled exception when the syntax is converted to the Bicep IR.
This PR fixes up resource-typed params and outputs instance function support with three changes:
InstanceFunctionCallSyntax
is updated to support all resources, not just those of typeDeclaredResourceMetadata
.EmitLimitationCalculator
to raise an error diagnostic when an instance function is called on a resource-typed module output, aslist*(reference(...).outputs. ...)
is blocked by ARM's dependency graph processor. (ThegetSecret()
function doesn't result in nested runtime functions and so is permitted.)Microsoft Reviewers: Open in CodeFlow