Problem: (I did search previous issues but could not see this discussion)
Sometimes when you are using AVM in your Bicep templates, you can be using old versions without realising it. Either through copying an old template or the VS Code extension for Bicep sometimes auto-selects the incorrect version that isn't the latest, you are none the wiser.
My suggestion is that we need a way to get notifications on non-latest Azure Verified Module usage in templates. Either by extending the current use-recent-api-versions to include similar linting warning for older AVM usage like:
I think the benefits of having -something- that helps us catch older AVM usage, would be beneficial to everyone. AVM is gaining a lot of popularity also.
Problem: (I did search previous issues but could not see this discussion)
Sometimes when you are using AVM in your Bicep templates, you can be using old versions without realising it. Either through copying an old template or the VS Code extension for Bicep sometimes auto-selects the incorrect version that isn't the latest, you are none the wiser.
My suggestion is that we need a way to get notifications on non-latest Azure Verified Module usage in templates. Either by extending the current
use-recent-api-versions
to include similar linting warning for older AVM usage like:Can we either get the
bicepconfig.json
:Or via an entirely new property within the
bicepconfig.json
to enable this, if technically possibly something like:I think the benefits of having -something- that helps us catch older AVM usage, would be beneficial to everyone. AVM is gaining a lot of popularity also.
Hope that makes sense.