Open pamelafox opened 1 year ago
Hi @pamelafox,
Template Analyzer supports only one of analyze-template
and analyze-directory
, but it looks like that scenario isn't handled properly here during invocation with environment variable overrides.
As a workaround, are you able to instead override the directory to the location of the infra directory so Template Analyzer finds that template and parameters file in a directory scan? (This would also result in scanning any other templates discovered in that directory or subdirectories.)
Thanks @JohnathonMohr for the suggestion. I've now run into this issue for a different repo where I need to specify a parameters file in a different location than the template, so that workaround won't work. (The reason for giving a different parameters file is that it's erroring on the standard one.)
I am trying to use the action to analyze a single template, so I specified env variables that seem to correspond to the usage described in https://github.com/Azure/template-analyzer:
However that results in a poorly formed command and subsequent error:
Here's the full workflow: https://github.com/pamelafox/simple-fastapi-container/actions/runs/4485952792/jobs/7887991866?pr=6
Can you clarify proper usage? Thanks!