-
Notifications
You must be signed in to change notification settings - Fork 167
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
Allow show
to work when no environment exists
#2379
Conversation
Today, `azd show` is used by VS Code to get information about the current project, both the services that make it up (and information about where the code for these services is) as well as the target resources (if we can determine them) In the case where an environment didn't exist (which is hard to have happen during a normal course of action, but possible if you manually go mucking around in `.azure`) `azd show` would prompt the user if they wanted to go create an environment. This caused issues with the VS integration, since the editor would not expect `azd` to prompt in this case. `azd show` already handles the case where the infrastructure for a project has not been deployed. This change extends this behavior so that if for some reason we can not fetch the current environment, we just return information about the services that we can discover Fixes Azure#2296 Fixes Azure#851
@bwateratmsft, this change does what we discussed over teams. If we can't fetch information about the environment, we just return information about the projects on disk, similar to the case where we can't fetch resource information because |
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSIContainer
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference (preview)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ellismg tested it out and it worked great. Also went and created an environment afterward and that also went good.
Today,
azd show
is used by VS Code to get information about the current project, both the services that make it up (and information about where the code for these services is) as well as the target resources (if we can determine them)In the case where an environment didn't exist (which is hard to have happen during a normal course of action, but possible if you manually go mucking around in
.azure
)azd show
would prompt the user if they wanted to go create an environment.This caused issues with the VS integration, since the editor would not expect
azd
to prompt in this case.azd show
already handles the case where the infrastructure for a project has not been deployed. This change extends this behavior so that if for some reason we can not fetch the current environment, we just return information about the services that we can discoverFixes #2296
Fixes #851