You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From various bits of documentation, discussions and issues, I've got the impression that the infra modules for services do not need to be referenced by the main module in order to be deployed.
The ACA templates reference the service modules in main.bicep despite this answer from January stating that:
Note that this bicep file does not need to be referenced by main.bicep.
I've created a project from an ACA template, modified it until it creates the resources I need and it deploys mostly fine using azd up. However, if I omit the service infra modules from the main module, a fresh azd deploy fails with an error saying that resources with the appropriate service tags cannot be found.
This also means that when I'm iterating the container app settings, I have to run a full azd up every time for the infra changes to be picked up. Running all the infra deployments every time is slow, even if no actual changes get made.
I guess the gist of my question is, how is the service infra module deployment supposed to work with ACA? Does it have to always be a full provision + deploy cycle?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
From various bits of documentation, discussions and issues, I've got the impression that the infra modules for services do not need to be referenced by the main module in order to be deployed.
The ACA templates reference the service modules in
main.bicep
despite this answer from January stating that:I've created a project from an ACA template, modified it until it creates the resources I need and it deploys mostly fine using
azd up
. However, if I omit the service infra modules from the main module, a freshazd deploy
fails with an error saying that resources with the appropriate service tags cannot be found.This also means that when I'm iterating the container app settings, I have to run a full
azd up
every time for the infra changes to be picked up. Running all the infra deployments every time is slow, even if no actual changes get made.I guess the gist of my question is, how is the service infra module deployment supposed to work with ACA? Does it have to always be a full provision + deploy cycle?
Beta Was this translation helpful? Give feedback.
All reactions