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
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.
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)
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?
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
The text was updated successfully, but these errors were encountered: