Closed paulyuk closed 1 year ago
That's fair - I think it's pretty low touch for us to just have a blurb at the top of provision output (where the grey text lives now) that says something like:
"Provisioning in rg in region using subscription" (where rg, region, subscription are placeholders)
or similar.
@Austinauth for his thoughts as well.
I guess my follow up would be: does RG need to be in that blurb if it's printed out as the first thing in the provision output?
If there is valid concern about not knowing which region or subscription you're provisioning and deploying to beyond the initial azd up
, would it be worth having users confirm the region and subscription before executing the command every time?
@ellismg @savannahostrowski adding it to the Germanium bucket. We can pull it into iterations/sprints as part of planning.
Hey everyone, I intend to work on this as a part of Hacktoberfest but I have a question.
Your request is to print the subscription before the resource group when someone runs any of the 2 commands azd up or azd provision. Am I correct?
Once you've done the azd up or provision once, the subscription and region you chose is stashed away in the environment files.
At scale, when working with enough environments, it gets painful to know which subscription/region/token you're targeting.
The request is to always print the RG/subscription/region in every provision and up, so you know where you're sending those bits. This is incredibly useful for diagnostics and communication.
@jongio @ellismg @savannahostrowski