Add support to deploy Bicep modules as a service instead of infra

[ronaldbosma]

I use Bicep to deploy APIs in API Management. I consider these to be part of my application, not part of the infrastructure.

With the current setup, I need to deploy these when provisioning the infra using azd provision. It would be great to be able to separate this Bicep configuration in a module that can be deployed as a service as part of the application when running azd deploy.

The file structure could be something like this. The main.parameters.json could use the environment variables to set the necessary parameters.

/infra
  ...
/src
  /myApi
    main.bicep
    main.parameters.json
    ...

Then include it in the azure.yaml like so (not sure what the host would be):

services:
  myApi:
    project: ./src/myApi
    host: ???
    language: bicep

[NanaXiong00]

@ronaldbosma The behavior is per design. The azd provision command creates resources based on the code in infra/main.bicep, and the azd deploy command uploads the application code for deployment.

@rajeshkamal5050 Users want to deploy API Management Bicep configurations as services when running azd deploy, rather than deploying infrastructure via azd provision. Should we consider marking this as an enhancement issue?