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

[SHACK-145] rename remote connection to target host #94

Conversation

marcparadise
Copy link
Member

This is a global rename of Connection to TargetHost. TargetHost is a more accurate representation, since it exposes information about the host and actions to perform against the host. The connection itself is internal to it.

The class and 'connection/conn' variables + accessors were renamed to TargetHost and target_host respectively.

Given our usage, TargetHost makes more sense - it's a representation
of the remote host that contains a connection, as opposed to being
an actual connection itself.
@marcparadise marcparadise requested a review from a team April 26, 2018 16:11
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
@marcparadise marcparadise force-pushed the SHACK-145/multitarget/rename-remote-connection-to-target-host branch from 4c6d49b to 3ea05e3 Compare April 26, 2018 16:22
Copy link
Contributor

@jonsmorrow jonsmorrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@marcparadise marcparadise merged commit 8d4beff into master Apr 26, 2018
@marcparadise marcparadise deleted the SHACK-145/multitarget/rename-remote-connection-to-target-host branch April 26, 2018 17:02
@marcparadise marcparadise restored the SHACK-145/multitarget/rename-remote-connection-to-target-host branch April 26, 2018 17:02
@chef-ci chef-ci deleted the SHACK-145/multitarget/rename-remote-connection-to-target-host branch April 26, 2018 17:03
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

Successfully merging this pull request may close these issues.

2 participants