Old Location-Should-Not-Be-Hardcoded Test is no longer valid
Open
bug
- Dominant language
- PowerShell
- Stars
- 468
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Description
We have a [test](unit-tests\Location-Should-Not-Be-Hardcoded\Fail\inner-scope-resource.json) that no longer causes errors, because we are no longer checking deploymentTemplates due to changes in bicep behavior.
For the moment, I believe we simply want to remove the test.
Unfortunately, the test highlights a scenario we could do a better job of checking: that an actual hardcoded value exists for a resource group.
If you would like to change the behavior of Location-Should-Not-Be-Hardcoded to accomplish this, please let me know.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.