finops-toolkit icon indicating copy to clipboard operation
finops-toolkit copied to clipboard

Deploy to Azure Gov v0.10 (Error - Symbolic name requires API min 2020-09-01)

Open bradlovas opened this issue 6 months ago â€ĸ 11 comments

🐛 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:

  1. Go to https://microsoft.github.io/finops-toolkit/hubs
  2. Click on "Deploy to Azure Gov" deployment option
  3. Scroll down to
  4. 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

Image

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:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

bradlovas avatar May 08 '25 12:05 bradlovas

@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.

flanakin avatar May 08 '25 14:05 flanakin

Sharing a screenshot from @l3hMichaelPeterson that points to the Validate API: Screenshot of the Validate API call that is failing

See #1577

flanakin avatar May 10 '25 00:05 flanakin

FYI - Support is engaged and I also looped in the team that owns the Validate API.

flanakin avatar May 10 '25 00:05 flanakin

@allcontributors please add @bradlovas for bug

flanakin avatar May 10 '25 00:05 flanakin

@allcontributors please add @l3hMichaelPeterson for bug

flanakin avatar May 10 '25 00:05 flanakin

@flanakin

I've put up a pull request to add @bradlovas! :tada:

allcontributors[bot] avatar May 10 '25 00:05 allcontributors[bot]

@flanakin

I've put up a pull request to add @l3hMichaelPeterson! :tada:

allcontributors[bot] avatar May 10 '25 00:05 allcontributors[bot]

FWIW having same issue. Will wait to deploy to GOV until this is resolved. Thanks.

lundejd avatar Jun 24 '25 14:06 lundejd

@lundejd This is a portal or possibly an ARM bug. Can you deploy via command line?

flanakin avatar Jun 25 '25 07:06 flanakin

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.

Image

lundejd avatar Jul 16 '25 00:07 lundejd

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.

Image Image

vs.

Image

ctcordas avatar Aug 27 '25 16:08 ctcordas