Jira (FACT-2102) Google Compute Engine metadata facts need endpoint change <= 2.5.6

7 views
Skip to first unread message

Eric Johnson (JIRA)

unread,
Nov 4, 2019, 9:18:02 AM11/4/19
to puppe...@googlegroups.com
Eric Johnson created an issue
 
Facter / Bug FACT-2102
Google Compute Engine metadata facts need endpoint change <= 2.5.6
Issue Type: Bug Bug
Affects Versions: FACT 2.5.1, FACT 2.5.2
Assignee: Gabriel Nagy
Created: 2019/11/04 6:17 AM
Environment:

Ruby-based facter versions <= 2.5.6

Priority: Major Major
Reporter: Eric Johnson

Google Compute Engine's internal metadata service will be deprecating the 'v1beta1' endpoint sometime before end of calendar year 2019. The GCE metadata-helper[1] should be updated to use the 'v1' endpoint instead.

 

NOTE: FACT-2018 addressed this issue for Facter 3.x, but the ruby based 2.x also needs to be fixed.

 

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/2.x/lib/facter/gce/metadata.rb#L20

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Mihai Buzgau (JIRA)

unread,
Nov 14, 2019, 6:52:04 AM11/14/19
to puppe...@googlegroups.com

Eric Johnson (JIRA)

unread,
Nov 22, 2019, 12:03:05 PM11/22/19
to puppe...@googlegroups.com

Mihai Buzgau (JIRA)

unread,
Nov 27, 2019, 4:51:10 AM11/27/19
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages