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

CloudShell bash is created for each execution for playbook in CloudShell #42

Closed
kyliel opened this issue Dec 18, 2017 · 4 comments
Closed

Comments

@kyliel
Copy link

kyliel commented Dec 18, 2017

It seems a new CloudShell bash will be created once I execute "ansilbe: run Ansilbe Playbook in CloudShell". If one CloudShell bash was provisioned at the first time, could I continue to use that one?
image

Then next time the playbook is directly run on provisioned CloudShell and no need to show below "info" again.

image

BTW, could we only show "warn" message at the first time?
image

@yungez
Copy link
Collaborator

yungez commented Dec 18, 2017

To achieve consistent cloudshell terminal, need cloudshell sdk supports to get consistent cloudshell connection. otherwise, there's no way to determine whether a cloudshell session is still alive, even vscode terminal could be reused, user will met failure if cloudshell session timedout.

@yungez
Copy link
Collaborator

yungez commented Dec 18, 2017

and current behavior is aligning with Cloud shell extension behavior in Azure Account. I'm guessing they have same concern when doing this.

@yungezz
Copy link
Contributor

yungezz commented Mar 14, 2018

PR #94

@yungezz
Copy link
Contributor

yungezz commented Mar 23, 2018

published in v0.1.5. pls have a try and let us know if any issue. thanks again.

@yungezz yungezz closed this as completed Mar 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants