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

[Issue] Can't get environment outputs when doing azd env select in devcenter mode #3861

Open
markweitzel opened this issue May 6, 2024 · 2 comments · May be fixed by #3942
Open

[Issue] Can't get environment outputs when doing azd env select in devcenter mode #3861

markweitzel opened this issue May 6, 2024 · 2 comments · May be fixed by #3942
Assignees
Labels
ade Azure Deployment Environments bug Something isn't working
Milestone

Comments

@markweitzel
Copy link
Member

In devcenter mode, I do an azd env select <envname> and when this occurs, an error is returned and the environment does not get set correctly.

image

@ellismg
Copy link
Member

ellismg commented May 6, 2024

We failed to discover the outputs here because we could not find the corresponding ARM deployment in the deployment history for the resource group attached to the environment. That failed because there was a mismatch between what was in azure.yaml for platform.config.environmentType (which was Test) and what was tagged in the deployment object we intended to find (which was Dev).

I asked @markweitzel offline if he knew how these might have gotten out of sync.

It may be reasonable to say that you can azd env select an environment even if we couldn't find the corresponding deployment (I'll leave that as a question for @wbreza when he gets back, we allow this today outside of dev center mode) but even if we were to allow this azd env refresh would fail later in the end to end for @markweitzel's specific scenario, since there we really do need the deployment object to fetch the outputs.

After making the change to azure.yaml I was able to azd env select the environment and run azd env refresh.

@rajeshkamal5050 rajeshkamal5050 added the ade Azure Deployment Environments label May 10, 2024
@rajeshkamal5050 rajeshkamal5050 added this to the Backlog milestone May 10, 2024
@wbreza wbreza linked a pull request May 21, 2024 that will close this issue
2 tasks
@wbreza wbreza self-assigned this May 21, 2024
@wbreza wbreza added the bug Something isn't working label May 21, 2024
@wbreza
Copy link
Contributor

wbreza commented May 21, 2024

This is not intentional. It looks like it is comparing the environment of the currently selected project instead of the matched remote ADE environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ade Azure Deployment Environments bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants