finops-toolkit
finops-toolkit copied to clipboard
Deploy to Azure Gov v0.10 (Error - Symbolic name requires API min 2020-09-01)
đ Problem
TODO: Now that FOCUS exports are supported for Gov cloud, my customer is trying to deploy the April update version 0.10 from this page using the "Deploy to Azure Gov" deployment option: https://microsoft.github.io/finops-toolkit/hubs and receives the following error:
ERROR Support for symbolic name resources requires a minimum API version of '2020-09-01' but API version '2020-06-01' was supplied. (Code : InvalidDeployment)
đŖ Repro steps
TODO: Add repro steps below:
- Go to https://microsoft.github.io/finops-toolkit/hubs
- Click on "Deploy to Azure Gov" deployment option
- Scroll down to
- See error Support for symbolic name resources requires a minimum API version of '2020-09-01' but API version '2020-06-01' was supplied. (Code : InvalidDeployment)
đ¤ Expected
TODO: Add a clear and concise description of what you expected to happen. Deployment to succeed.
đˇ Screenshots
TODO: If applicable, add screenshots to help explain your problem. Remove if not applicable.
âšī¸ Additional context
TODO: Add any other context about the problem here. Remove if not applicable.
đââī¸ Ask for the community
We could use your help:
- Please vote this issue up (đ) to prioritize it.
- Leave comments to help us solidify the vision.
@bradlovas I just investigated this. I believe this is happening because of the Batch API the Azure portal uses. That's the only reference to 2020-06-01 I could find. We don't use that API version in any of our code so I don't think it has anything to do with the template itself.
It is curious that it's only an issue in Azure Gov, so I'm not sure if it's a configuration issue in ARM or something the Azure portal needs to change, tho. Can you file this as a support request on the Azure portal team? Feel free to include my name.
Sharing a screenshot from @l3hMichaelPeterson that points to the Validate API:
See #1577
FYI - Support is engaged and I also looped in the team that owns the Validate API.
@allcontributors please add @bradlovas for bug
@allcontributors please add @l3hMichaelPeterson for bug
FWIW having same issue. Will wait to deploy to GOV until this is resolved. Thanks.
@lundejd This is a portal or possibly an ARM bug. Can you deploy via command line?
Tried via PowerShell following the install directions, got the following error:
Cannot bind argument to parameter 'Path' because it is null.
I see this has been an issue for others in a separate issue post so this is just FYI, have no options.
Similar issues for me in Gov on v.0.11. In my case, I am missing 5 pipelines and need to rerun the deployment to see if that adds them.
vs.