We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Referencing outputs from a Bicep module produces a warning:
Warning: The parsing of the template output named <output name> failed`
For a large codebase we get thousands of these warnings, making the output huge. This feels like a bug.
I expect that the output either can be parsed, or if it is impossible to handle outputs like this it should be possible to silence these warnings.
Given the following main.bicep file:
main.bicep
module dummy 'dummy.bicep' = { name: 'dummy' params: { dummy: 'dummy' } } output dummy string = dummy.outputs.dummy
And the following module dummy.bicep:
dummy.bicep
param dummy string output dummy string = dummy
Then run TemplateAnalyzer on main.bicep.
TemplateAnalyzer version 0.7.0+582d9199d19acc60716af8f0874dc51cec6aa01b
0.7.0+582d9199d19acc60716af8f0874dc51cec6aa01b
Same issue on my local system (Ubuntu WSL on Windows) and in an Azure DevOps pipeline using the MicrosoftSecurityDevOps@1 task.
MicrosoftSecurityDevOps@1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Referencing outputs from a Bicep module produces a warning:
For a large codebase we get thousands of these warnings, making the output huge. This feels like a bug.
Expected behavior
I expect that the output either can be parsed, or if it is impossible to handle outputs like this it should be possible to silence these warnings.
Reproduction Steps
Given the following
main.bicep
file:And the following module
dummy.bicep
:Then run TemplateAnalyzer on
main.bicep
.Environment
TemplateAnalyzer version
0.7.0+582d9199d19acc60716af8f0874dc51cec6aa01b
Same issue on my local system (Ubuntu WSL on Windows) and in an Azure DevOps pipeline using the
MicrosoftSecurityDevOps@1
task.The text was updated successfully, but these errors were encountered: