Would be nice if I could specify the deployment target of a service to an output from my Bicep deployment

[mbenko]

``The azure.yaml file includes a project: attribute that defines where the code for the service lives and the language attribute tells me how to build it. It would be nice if I could specify the destination name of the azure service I'd like to deploy to. The data could be stored in the environment configuration (resource group name, etc). Also would be nice to specify the name of the resource group to deploy to. something like

services:
  web:
    project: myApp
    language: csharp
    host: appservice
    hostname: outputs.siteName

[markweitzel]

This is interesting... One thing we are looking at is determining when to use theexisting tag in bicep. Existing Resources in Bicep

So we probably could piece this together today, but it would be more manual than we'd like. For example, you could create the environment--which maps the resource group name. Then in the bicep, add the existing = tag. If you have an existing resource group with the same name, it should use that one.

[mbenko]

The outputs.siteName isn't meant to refer to an existing resource, but rather the outputs section from the IaC code. When I create a resource in Bicep I can define an output variable that is the name of that resource. Then the deployment from azd would use that name as the target for publishing the code instead of using a convention. In Terraform I can define an output as well. Same in ARM.