-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue] Enable azure.yaml to specify optional deployments for services #3514
Comments
Related #3272 |
Part of me wonders if we should try to model this as conditions on steps in a workflow (now that we are moving down that path with how |
If represented as a workflow user could manually call |
My company needs this as well. Do you think I can do a PR using the condition design above? |
For the record, we are currently "achieving" this for a public code template by having the host line commented out, asking developers to un-comment it, and also by providing a azd environment variable that turns on the relevant Bicep modules. It's not super elegant, but it's the least code approach we could find: @codeazon I'm curious as to your company's needs, you have situations where you sometimes want to deploy to some hosts and sometimes to others? We thought that maybe such a situation was only common for public templates with disparate developers using them. |
We want to deploy some services, but not all. For example, in dev environment, only need to deploy Service A and Service B. |
Thank you for the feedback! It seems we have a couple of strong options to consider in supporting this feature request:
I’m leaning towards option 2, as it offers more flexibility for end users. This would address the selective deployment scenario and could also support other use cases where only a subset of azd commands need to be executed. |
Our situation: we have an appservice host, and if the user sets a current azd variable, we also want to deploy a functionapp for an additional microservice.
We discussed this in an internal teams thread here:
https://teams.microsoft.com/l/message/19:[email protected]/1708030654691?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=c99e8504-1250-4d95-a824-9778e0e626c7&parentMessageId=1708030654691&teamName=Azure%20Developer%20CLI%20(azd)%20Partners&channelName=General&createdTime=1708030654691
Here's a syntax that Victor suggested:
That would work perfectly for our use case.
And he even suggested that we could switch the platform (like to change between AppService and ACA):
Without this feature, I think we will end up having to use the Azure CLI for the deployment, or forcing developers to un-comment, which is quite inelegant and prone to error.
Thanks!
The text was updated successfully, but these errors were encountered: