`containerapp compose create` is not respecting the --location argument

[charris-msft]

Related command

az containerapp compose create

Extension name (the extension in question)

containerapp-compose

Description of issue (in as much detail as possible)

When running the command and specifying a location via -l or --location it ignores the specified location and defaults to 'westus3' which "is not currently supported".

That value is not coming from my param-persist either:

---

[yonzhan]

route to CXP team

[usepowershell]

@charris-msft What versions of the extensions (containerapp and containerapp-compose) do you have installed?

[charris-msft]

@smurawski

Name                  Path                                                        Preview    Version
--------------------  ----------------------------------------------------------  ---------  ---------
containerapp          C:\Users\charris\.azure\cliextensions\containerapp          True       0.3.9
containerapp-compose  C:\Users\charris\.azure\cliextensions\containerapp-compose  True       0.2.0

[usepowershell]

@charris-msft

I'm finding another bug in the 0.3.9 that has blocked me from testing so far ( #5253 ) , but I was able to deploy successfully to Canada Central with the containerapp extension at 0.3.8 and 0.3.7.

I'll continue to check with 0.3.9 with a private image shortly.

[usepowershell]

@charris-msft

I've confirmed your problem - it appears that the resource group location is overriding command line provided location arguments - which appears to be happening regardless of containerapp extension version. I'll investigate further.

[charris-msft]

@smurawski I tested by moving my existing resources to a new rg in the location where I wanted to create the new containerapp, ran the command and it didn't error out this time. (still running)

[usepowershell]

This is fixed in #5262 (version 0.2.1) which is available now.

[charris-msft]

Looks like it's working - it created the ACA Environment in the correct location.

Though because I'm still getting prompted my registry credentials (which I don't know), I can't confirm that the ACA gets created in the correct location as well.

[usepowershell]

Thanks @charris-msft ! The registry credentials prompting should be fixed once v0.3.10 of the containerapp extension ships.

The PR for that is here - #5241

[RakeshMohanMSFT]

@charris-msft and @smurawski can we close this issue, i see that the PR is merged.

[charris-msft]

I did some more testing and I'm comfortable closing it.