Skip to content
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

resourceGroup in azure.yaml not honored for rg-scoped deployment #4287

Open
weikanglim opened this issue Sep 3, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working core
Milestone

Comments

@weikanglim
Copy link
Contributor

  1. azd env new to create a new environment
  2. Set resourceGroup: <some group> in azure.yaml.
  3. Run azd provision

Expected:
The resourceGroup property is used.

Actual:
I get prompted for a resource group to be selected.

@rajeshkamal5050 rajeshkamal5050 added core bug Something isn't working labels Sep 4, 2024
@rajeshkamal5050 rajeshkamal5050 added this to the Sep 2024 milestone Sep 4, 2024
ellismg added a commit to ellismg/azure-dev that referenced this issue Sep 13, 2024
We allow specifying the resource group which is used for discovery of
resources (instead of probing for a resource group taged with
`azd-env-name` inside `azure.yaml`. When doing a resource group scoped
deployment, we should consider this value if set and use it instead of
prompting the user to select a resource group or create a new one.

Fixes Azure#4287
@ellismg ellismg modified the milestones: Sep 2024, Oct 2024 Oct 14, 2024
@rajeshkamal5050 rajeshkamal5050 modified the milestones: Oct 2024, Nov 2024 Nov 7, 2024
@aviflax
Copy link

aviflax commented Nov 11, 2024

I just ran into this as well and it was perplexing.

@rajeshkamal5050 rajeshkamal5050 modified the milestones: Nov 2024, Dec 2024 Dec 2, 2024
@ellismg ellismg modified the milestones: Dec 2024, Backlog Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working core
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants