Closed slavizh closed 2 years ago
Is this different than #20?
@alex-frankel no, but I thought with the last release #20 was addressed but may be I have understood the notes differently.
@alex-frankel My takeaways from #20 and his have been slightly different. The fix addressed for #20 was for the fact that when stack deployments were running, verbose logs (and even debug logs for that matter) were not being printed at all when -verbose (or -debug) were passed, and with no progress of any kind shown on the shell, it could seem like it was not responding. That shouldn't be the case anymore. This issue I see more as regarding the contents of the logs being printed and to have deployment status in the verbose logs as is the case with deployments cmdlets. I will be working on this. @slavizh please let me know if I have missed anything in my read of this issue.
@Xynoclafe yes. I have provided more info around the whole deployment stacks cmdlet experience and what should be on par with deployment cmdlets in #46
going to remove this one as I think we have it covered between #20 and #46
Describe the bug I am deploying budget for cost management but the progress of the resource deployed is missing. It does not show even Microsoft.Resources/deployments progress.
To Reproduce
Expected behavior To show like this:
Repro Environment Host OS: Windows 11 Powershell Version: PowerShell 7.2
Server Debugging Information Correlation ID: c3935ce9-effe-46d4-a7e4-fb4b1165f527 Tenant ID: Timestamp of issue (please include time zone): - 2021-12-06T07:23:31.2117237Z - UTC Data Center (eg, West Central US, West Europe): West Europe