With both me and icco@ departing Google fog-google no longer has a CI stack as we don't have access to a sponsored GCP account anymore and I've been unsuccessful in finding someone who would volunteer to maintain this project or CI at the time of my departure.
There is no easy way to say this but we need help as costs of running a CI stack that touches almost all GCP resources is significant. We know there's a lot of companies out there that are using this lib, as well as tooling based on it so if you want to help us with running a CI stack or provide sponsorship for a GCP account - please contact me at code <at> temik.me
--
Artem (temikus@) - Lead maintainer
The main maintainers for the Google sections are @icco, @Temikus and @plribeiro3000. Please send pull requests to them.
-
As of v1.0.0, fog-google includes google-api-client as a dependency, there is no need to include it separately anymore.
-
Fog-google is currently supported on Ruby 2.4+ See supported ruby versions for more info.
See MIGRATING.md for migration between major versions.
There are two ways to access Google Cloud Storage. The old S3 API and the new JSON API. Fog::Storage::Google will automatically direct you to the appropriate API based on the credentials you provide it.
- The XML API is almost identical to S3. Use Google's interoperability keys to access it.
- The new JSON API is faster and uses auth similarly to the rest of the Google Cloud APIs using a service account private key.
Google Compute Engine is a Virtual Machine hosting service. Currently it is built on version v1 of the GCE API.
As of 2017-12-15, we are still working on making Fog for Google Compute engine (Fog::Compute::Google) feature complete. If you are using Fog to interact with GCE, please keep Fog up to date and file issues for any anomalies you see or features you would like.
Fog implements v1beta4 of the Google Cloud SQL Admin API. As of 2017-11-06, Cloud SQL is mostly feature-complete. Please file issues for any anomalies you see or features you would like as we finish adding remaining features.
Fog implements v1 of the Google Cloud DNS API. We are always looking for people to improve our code and test coverage, so please file issues for any anomalies you see or features you would like.
Fog implements v3 of the Google Cloud Monitoring API. As of 2017-10-05, we believe Fog for Google Cloud Monitoring is feature complete for metric-related resources and are working on supporting groups.
We are always looking for people to improve our code and test coverage, so please file issues for any anomalies you see or features you would like.
Fog mostly implements v1 of the Google Cloud Pub/Sub API; however some less common API methods are missing. Pull requests for additions would be greatly appreciated.
Add the following two lines to your application's Gemfile:
gem 'fog-google'And then execute:
$ bundleOr install it yourself as:
$ gem install fog-googleIntegration tests can be kicked off via following rake tasks. Important note: As those tests are running against real API's YOU WILL BE BILLED.
rake test # Run all integration tests
rake test:parallel # Run all integration tests in parallel
rake test:compute # Run Compute API tests
rake test:monitoring # Run Monitoring API tests
rake test:pubsub # Run PubSub API tests
rake test:sql # Run SQL API tests
rake test:storage # Run Storage API tests
Since some resources can be expensive to test, we have a self-hosted CI server.
Due to security considerations a repo maintainer needs to add the label integrate to kick off the CI.
Follow the instructions to generate a private key. A sample credentials file can be found in .fog.example in this directory:
cat .fog.example >> ~/.fog # appends the sample configuration
vim ~/.fog # edit file with yout config
As of 1.9.0 fog-google supports Google application default credentials (ADC)
The auth method uses Google::Auth.get_application_default
under the hood.
Example workflow for a GCE instance with service account scopes defined:
> connection = Fog::Compute::Google.new(:google_project => "my-project", :google_application_default => true)
=> #<Fog::Compute::Google::Real:32157700...
> connection.servers
=> [ <Fog::Compute::Google::Server ... ]
It is common to integrate Fog with Carrierwave. Here's a minimal config that's commonly put in config/initializers/carrierwave.rb:
CarrierWave.configure do |config|
config.fog_provider = 'fog/google'
config.fog_credentials = {
provider: 'Google',
google_project: Rails.application.secrets.google_cloud_storage_project_name,
google_json_key_string: Rails.application.secrets.google_cloud_storage_credential_content
# can optionally use google_json_key_location if using an actual file;
}
config.fog_directory = Rails.application.secrets.google_cloud_storage_bucket_name
end
This needs a corresponding secret in config/secrets.yml, e.g.:
development:
google_cloud_storage_project_name: your-project-name
google_cloud_storage_credential_content: '{
"type": "service_account",
"project_id": "your-project-name",
"private_key_id": "REDACTED",
"private_key": "-----BEGIN PRIVATE KEY-----REDACTED-----END PRIVATE KEY-----\n",
"client_email": "REDACTED@your-project-name.iam.gserviceaccount.com",
"client_id": "REDACTED",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/REDACTED%40your-project-name.iam.gserviceaccount.com"
}'
google_cloud_storage_bucket_name: your-bucket-name
If you want to be able to bootstrap SSH-able instances, (using servers.bootstrap,) be sure you have a key in ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub
Once you've specified your credentials, you should be good to go!
$ bundle exec pry
[1] pry(main)> require 'fog/google'
=> true
[2] pry(main)> connection = Fog::Compute::Google.new
[3] pry(main)> connection.servers
=> [ <Fog::Compute::Google::Server
name="xxxxxxx",
kind="compute#instance",
Fog-google is currently supported on Ruby 2.4+.
In general we support (and run our CI) for Ruby versions that are actively supported by Ruby Core - that is, Ruby versions that are not end of life. Older versions of Ruby may still work, but are unsupported and not recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby support schedule.
See CONTRIBUTING.md in this repository.