-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add communicator reset #10399
Add communicator reset #10399
Conversation
Properly order options alphabetically and include new option for reset.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
♻️ 👍 Looks good to me!
Awesome, thanks a lot! |
Thanks @chrisroberts! That was a fast turn around! 🎉 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Adds a
Communicator#reset!
method to allow resetting the communicator to force establishing a new connection. Fixes linux docker install to reset communicator after group updates sovagrant
user hasdocker
group available. Includes new option:reset
to the shell provisioner to allow resetting the connection after a provisioner has completed. Also allows a provisioner to run without apath
orinline
defined simply to reset the connection.Fixes #10388