[GCE Discovery] Automatically set project-id and zone#33721

Merged

vladimirdolzhenko merged 21 commits intoelastic:masterfrom vladimirdolzhenko:13618

Oct 3, 2018

+635-19

Commits on Sep 14, 2018

Automatically set project-id and zone
Vladimir Dolzhenko
committed
adjust doc: project id and zone are not mandatory
Vladimir Dolzhenko
committed

Commits on Sep 18, 2018

add the reason of copy-n-paste from GCE SDK
Vladimir Dolzhenko
committed
headerContainsMetadataFlavor test is added
Vladimir Dolzhenko
committed
note that it doesn't try to use any system properties and/or env variables
Vladimir Dolzhenko
committed
imports!
Vladimir Dolzhenko
committed
headerContainsMetadataFlavor test is added
Vladimir Dolzhenko
committed
use diff GceMetadataService.GCE_HOST to avoid resolving default values from metadata service
Vladimir Dolzhenko
committed
add test with a real http server for testMetadataServerValues
Vladimir Dolzhenko
committed

Commits on Sep 21, 2018

Added QA test for discovery-gce
Vladimir Dolzhenko
committed
some fixture polish
Vladimir Dolzhenko
committed

Commits on Sep 25, 2018

Merge remote-tracking branch 'remotes/origin/master' into 13618
Vladimir Dolzhenko
committed

Commits on Sep 28, 2018

drop GceInstancesServiceTests as QA test covers same functionality while unit tests don't spot all issues
Vladimir Dolzhenko
committed
grammar fix: a gce service
Vladimir Dolzhenko
committed
use jsonBuilder to generate json responses
Vladimir Dolzhenko
committed
explain gce specific settings rerouted to fixture
Vladimir Dolzhenko
committed
system property es.allow_reroute_gce_settings could be used to expose GCE-specific settings: cloud.gce.host and cloud.gce.root_url
Vladimir Dolzhenko
committed
Merge remote-tracking branch 'remotes/origin/master' into 13618
Vladimir Dolzhenko
committed

Commits on Oct 1, 2018

add the test purposes only note to ALLOW_REROUTE_GCE_SETTINGS
Vladimir Dolzhenko
committed
polished doc wording
Vladimir Dolzhenko
committed
renamed project() -> projectId()
Vladimir Dolzhenko
committed