-
Type:
Bug
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: FACT 3.14.5, FACT 3.13.4, FACT 3.11.10
-
Component/s: None
-
Labels:
-
Template:customfield_10700 324465
-
Team:Night's Watch
-
Story Points:2
-
Sprint:NW - 2019-10-02, PR - Triage
-
Method Found:Needs Assessment
-
Release Notes:Known Issue
-
Release Notes Summary:Google Compute Engine's internal metadata service will be deprecating the 'v1beta1' endpoint sometime before the end of 2019. Facter now uses the 'v1' endpoint instead.
-
QA Risk Assessment:Needs Assessment
Google Compute Engine's internal metadata service will be deprecating the 'v1beta1' endpoint sometime before end of calendar year 2019. The GCE resolver[1] should be updated to use the 'v1' endpoint instead.
Note that using the 'v1' endpoint also requires setting a custom User-Agent header that was not necessary in the old 'v1beta1' endpoint. Using 'curl' in a simple bash script as an example, I would need to change,
curl http://metadata.google.internal/computeMetadata/v1beta1/instance/name
to this,
curl -H "Metadata-flavor: Google" http://metadata.google.internal/computeMetadata/v1/instance/name
For more details about GCE metadata, please see https://cloud.google.com/compute/docs/storing-retrieving-metadata
[1] https://github.com/puppetlabs/facter/blob/master/lib/src/facts/resolvers/gce_resolver.cc#L243
- is cloned by
-
FACT-2102 Google Compute Engine metadata facts need endpoint change <= 2.5.6
-
- Resolved
-