-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Automatically set project-id and zone #13618
Comments
@dadoonet could you clarify what needs doing here? The first point sounds like that a value for |
Yes.
Indeed but if not set we can just fill that list with the current zone only which is I believe what users are doing most of the time I guess: deploying in one single zone. |
Ah right. I was thinking more about AWS availability zones of which it's best to use more than 1, but if that's a common way to use GCE then that makes sense. |
com.google.cloud.ServiceOptions#getDefaultProjectId tries to resolve project based on
ES assumes system properties as unsafe while environment variables could be predefined (e.g. for ECS Task IAM profile credentials in repository-s3 plugin) on the environment (could it be different from value returned from Are we going to use only last method ? |
Fetch default values for project-id and zone from metadata server Closes #13618
Fetch default values for project-id and zone from metadata server Closes #13618
The project id can be retrieved from the running instance by calling
http://metadata.google.internal/computeMetadata/v1/project/project-id
.Same for the default zone:
http://metadata.google.internal/computeMetadata/v1/project/attributes/google-compute-default-zone
No need then to force them in
elasticsearch.yml
.The text was updated successfully, but these errors were encountered: