search

Azure / deployment-stacks

Contains Deployment Stacks CLI scripts and releases
MIT License
87 stars 6 forks source link

When using -Verbose resources are not moving from running to succeded status, they only have succeeded #105

Open slavizh opened 1 year ago

slavizh commented 1 year ago

As you can see from the screenshot the resources do not move from running state to succeeded. They just appear as succeeded. For example you can see that deployments go from running to succeeded. This is different from New-*Deployment commands where you can see resources going from running to succeeded. I can also see that for some (not all) the same resource listed twice as succeeded which may be it is some kind of bug that one of the entries could be for running state but not outputted correctly. For example VM is listed twice as succeeded but the disk is listed only one.

image

azcloudfarmer commented 12 months ago

Hi @slavizh - we investigated the issues mentioned and found that the deployment operations are being pulled from the deployment service and changes/improvements would be required outside of the deployment stacks service. We acknowledge this issue but is currently a lower priority on the Deployment Stacks side.

slavizh commented 11 months ago

@azcloudfarmer ok but keep in mind that the information shown is misleading. If that progress is the same progress for regular deployments + stack progress wouldn't be easier to use the same approach that new-az*Deployment cmdlets are using to get that information? It seems like the stack cmdlets are using some other approach and thus having issues.