-
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
command/agent: Google Compute Engine host discovery #2570
Conversation
WIPing this as looks like using the command off the command line is not working - will update soon! |
This commit adds several command-line and config options that facilitate host discovery through Google Compute Engine (GCE), much like the recently added EC2 host discovery options. This should assist with bootstrapping and joining servers within GCE when non-static addresses are used, such as when using managed instance groups. Documentation has also been added. It should be noted that if running from within a GCE instance, the only option that should be necessary is -retry-join-gce-tag-value.
Add Google API and related dependencies for GCE discovery.
WIP removed - fixed the formatting on the help text and ensured that GCE discovery was actually detected in the same way that EC2 is (ie: adding the presence of the tag value to the same |
Thanks for the PR, @vancluever! This is a nice piece of functionality to have alongside the EC2 join stuff. |
No prob and thanks for the merge @kyhavlov! |
@vancluever I've got a question regarding your PR since I'm moving your code to https://github.com/hashicorp/go-discover. You name the override parameter for the project |
This PR adds several command-line and config options that facilitate host discovery through Google Compute Engine (GCE), much like the recently added EC2 host discovery options. This should assist with bootstrapping and joining servers within GCE when non-static addresses are used, such as when using managed instance groups.
Documentation has also been added. It should be noted that if running from within a GCE instance, the only option that should be necessary is
-retry-join-gce-tag-value
.