-
Notifications
You must be signed in to change notification settings - Fork 495
(FACT-1557) Extend the cloud.provider fact to Google Compute Engine #2479
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
(FACT-1557) Extend the cloud.provider fact to Google Compute Engine #2479
Conversation
|
Can one of the admins verify this patch? |
|
@natemccurdy could you prepend |
fb031d8 to
0f5df2e
Compare
@joshcooper Done. Thanks for looking! |
0f5df2e to
cbbda1c
Compare
|
Offering given to the Rubocop gods, tests updated for lint failures, and branch force pushed. The rubocop tests should pass now. |
cbbda1c to
4e7db5e
Compare
|
Guess I didn't make the right offering, sorry RuboCop gods. |
|
@joshcooper What do you recommend I do about the new RuboCop warnings? |
|
@natemccurdy could you add exclusions for those files to |
4e7db5e to
71be25d
Compare
Done 👍 |
joshcooper
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified this behaves as expected on GCE:
~/facter# bundle exec facter cloud.provider
gce
and it has parity with other cloud providers facts like https://tickets.puppetlabs.com/browse/FACT-1441
Similar to #2475 , this allows the
cloud.providerfact to resolve on Google Compute Engine nodes togce.For example:
This partially resolves https://tickets.puppetlabs.com/browse/FACT-1557
Note that I chose to have this resolve to the string "
gce" because that's what the currentvirtualfact resolves to, so Facter/Puppet users are probably most familiar with "gce" meaning Google Compute Engine.