You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During IaC deployments or command execution in the Azure Cloud Shell, users may encounter disconnection issues, resulting in the loss of session logs displayed in the console. If the deployment completes or fails during the disconnection, users are forced to manually investigate the deployment state. This often leads to additional troubleshooting efforts and, in some cases, the need to restart parts of the process due to the absence of retained execution logs in the console.
While there are workarounds available to keep the session alive, these methods are not officially supported by Azure Cloud Shell and may introduce risks or complexities. I would like to inquire if the Azure team has plans to introduce a feature that addresses this limitation. Such a feature would bring significant value to users who rely on the Azure Cloud Shell for managing deployments and executing commands.
We are keen to understand if this feature is on the Azure roadmap and whether it aligns with Azure’s vision for enhancing Cloud Shell usability.
Expect behavior
Azure should introduce a native feature, similar to solutions available in AWS and GCP, that allows users to reconnect to a previous session and access the logs displayed prior to the disconnection. This feature would enable users to seamlessly continue monitoring their deployment or command execution without requiring additional investigation or process restarts. Implementing this functionality would greatly enhance user experience and reduce operational overhead during deployments and command executions in the Azure Cloud Shell.
The text was updated successfully, but these errors were encountered:
Current
During IaC deployments or command execution in the Azure Cloud Shell, users may encounter disconnection issues, resulting in the loss of session logs displayed in the console. If the deployment completes or fails during the disconnection, users are forced to manually investigate the deployment state. This often leads to additional troubleshooting efforts and, in some cases, the need to restart parts of the process due to the absence of retained execution logs in the console.
While there are workarounds available to keep the session alive, these methods are not officially supported by Azure Cloud Shell and may introduce risks or complexities. I would like to inquire if the Azure team has plans to introduce a feature that addresses this limitation. Such a feature would bring significant value to users who rely on the Azure Cloud Shell for managing deployments and executing commands.
We are keen to understand if this feature is on the Azure roadmap and whether it aligns with Azure’s vision for enhancing Cloud Shell usability.
Expect behavior
Azure should introduce a native feature, similar to solutions available in AWS and GCP, that allows users to reconnect to a previous session and access the logs displayed prior to the disconnection. This feature would enable users to seamlessly continue monitoring their deployment or command execution without requiring additional investigation or process restarts. Implementing this functionality would greatly enhance user experience and reduce operational overhead during deployments and command executions in the Azure Cloud Shell.
The text was updated successfully, but these errors were encountered: