Ensure safe access of output guards against missing value
property
#13162
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 #13160
Safe dereference of a module output (
mod.outputs.?foo
) is currently written to guard against conditional outputs with afalse
condition (i.e., it would be equivalent to writingmod.outputs.?foo.value
if Bicep didn't automatically inject the.value
into module output reference expressions). It currently doesn't guard against outputs whose value isnull
(which will cause the ARM engine to omit the.value
property).This PR updates the expression converter to make
mod.outputs.?foo
compile to something like[tryGet(tryGet(reference('mod').outputs, 'foo'), 'value')]
to ensure both cases described above evaluate tonull
when evaluated by the ARM engine.Microsoft Reviewers: Open in CodeFlow