-
Notifications
You must be signed in to change notification settings - Fork 7
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
Actual deployment error not surfaced #78
Labels
bug
Something isn't working
Comments
ghost
added
the
Needs: Triage 🔍
label
Jan 20, 2023
Here is how error looks if you deploy via New-Az*Deployment:
You can see what better structure it has and full information is surfaced. |
Hi @slavizh, thanks for the details, we've filed a fix for this one. |
@slavizh I'm closing this one as we are bubbling up the underlying error now. Please open another issue if you continue to experience this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I have previously reported this with previous private preview but seems still present. When you are deploying deployment stacks and there is error the actual error is not surfaced. Instead we are getting something like this:
I need to go to activity log for example (due to this issue #77) and check what it says there. There I can see the following:
This gives me information what is causing the actual failure. Deployment stacks needs to surface the actual error as having to go in Portal to see it is not good experience. Even if you use deployment stacks in automation is not good experience as than you will need to build some logic that upon failure you will need to check the deployment and/or the activity log in order to present the actual error. In automation scenarios that will result in building additional code, maintaining it and additional time the pipeline needs to run in order to fetch that information.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Actual error to be surfaced. If there are more than one errors all should be surfaced.
Screenshots
If applicable, add screenshots to help explain your problem.
Repro Environment
Host OS: Windows 11
Powershell Version: 7.3.1
Server Debugging Information
Correlation ID: 1d58bde5-82f0-4637-892b-07ca323cfb7b
Tenant ID: I can provide in private.
Timestamp of issue (please include time zone): above, Eastern Europe time zone
Data Center (eg, West Central US, West Europe): West Europe
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: