[Issue] Specify azure.yaml for azd up

[pamelafox]

• Make sure you've installed the latest version using instructions in the wiki

Discussed internally here:
https://teams.microsoft.com/l/message/19:ug5DKpbpRJbBtgoSQAXdynHgthpALgePNJ8wb5AI8HM1@thread.tacv2/1693328738998?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=c99e8504-1250-4d95-a824-9778e0e626c7&parentMessageId=1693328738998&teamName=Azure%20Developer%20CLI%20(azd)%20Partners&channelName=General&createdTime=1693328738998

I have a branch that makes it possible to deploy an App Service sample with Azure Container Apps, but don't want to necessarily replace the App Aervice option. I was thinking I could enable switching via an azd env set, but that would still leave the problem of azure.yaml specifying appservice. If azd up could point at different azure.yaml files, then I could tell folks to point at azure-aca.yaml, for example.

Considerations:

• Would the other yaml point at different infra?
• Could main.bicep know which yaml it was called with? (To avoid an additional azd env set USE_ACA)

[ellismg]

I think some generalized --project-file that allows you to change the name of azure.yaml or provide a path (which would stop our start in the CWD and walk up looking for an azure.yaml logic) could be very interesting.

Would the other yaml point at different infra?

This would be supported today, I think, by setting the module property on the infra section of azure.yaml

Could main.bicep know which yaml it was called with? (To avoid an additional azd env set USE_ACA)

Perhaps we could add an env section to azure.yaml, which could set environment variables like this? These are basically "project wide" values where as the ones in the .env file in the environment folder are environment specific.

[pamelafox]

cc @anthonychu