fog-google | Fog for Google Cloud Platform | GCP library

by fog Ruby Version: v1.17.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(8)Vulnerabilities Install Support

kandi X-RAY | fog-google Summary

fog-google is a Ruby library typically used in Cloud, GCP applications. fog-google has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

The main maintainers for the Google sections are @icco, @Temikus and @plribeiro3000. Please send pull requests to them.

Support

Quality

Security

License

Reuse

Support

fog-google has a low active ecosystem.

It has 97 star(s) with 139 fork(s). There are 14 watchers for this library.

It had no major release in the last 12 months.

There are 12 open issues and 206 have been closed. On average issues are closed in 872 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of fog-google is v1.17.0

Quality

fog-google has 0 bugs and 65 code smells.

Security

fog-google has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fog-google code analysis shows 0 unresolved vulnerabilities.

There are 13 security hotspots that need review.

License

fog-google is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

fog-google releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

fog-google saves you 8132 person hours of effort in developing the same functionality from scratch.

It has 16780 lines of code, 1405 functions and 520 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of fog-google

Get all kandi verified functions for this library.

fog-google Key Features

No Key Features are available at this moment for fog-google.

fog-google Examples and Code Snippets

No Code Snippets are available at this moment for fog-google.

Community Discussions

Trending Discussions on fog-google

Rails broken - bundle not working - ovirt-engine-sdk - ERROR: Failed to build gem native extension. Cloud9 AWS

`to_specs': Could not find 'railties' (>= 0) among 8 total gem(s) (Gem::LoadError)

no connection pool with primary found

Fog-google doesn't find credentials

Excon::Error::Socket: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A (OpenSSL::SSL::SSLError)

Why does Bundler refuse to accept a gem with no version specified?

All tests throwing TypeError: no implicit conversion of nil into String

Upgrade kaminari to 1.0.1 using rails admin and active_support

QUESTION

Rails broken - bundle not working - ovirt-engine-sdk - ERROR: Failed to build gem native extension. Cloud9 AWS

Asked 2019-Jul-30 at 09:49

I am working through the Ruby on Rails Tutorial (Rails5) by Michael Hartl in the AWS Cloud9 environment. I'm finishing chapter 11 now. (new to programming as well)

It appears I have broken something related to the Rails (or Ruby) system. I am no longer able to start the Rails server, test or console.

The error message I get usually starts with this, which I have not had any luck finding much information on here or via Google. ovirt-engine-sdk -v '4.2.3'

...

ANSWER

Answered 2018-Apr-09 at 13:04

So I was able to fix this by:

Installing libcurl developer version:

sudo yum install libcurl libcurl-devel

Once that was complete I ran bundle update which now made it further in the install - to fail at this point Installing pg 0.20.0 with native extensions Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

Running sudo yum install postgresql-devel resolved the pg 0.20.0 issue and I am now able to complete the bundle update and rails seems to be working again.
Rails server had an issue booting after all of this. This command got it working again: bin/rails db:migrate RAILS_ENV=development

After that the environment and rails all seems to be working fine again.

Source https://stackoverflow.com/questions/49728438

QUESTION

`to_specs': Could not find 'railties' (>= 0) among 8 total gem(s) (Gem::LoadError)

Asked 2019-Jul-04 at 22:49

I postes this question because I didn't find any related answer on stackoverflow. I did everything. I will explain what I have tried. When I start the Rails server using rails s, I get the following output:

...

ANSWER

Answered 2019-Jul-03 at 12:33

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

Source https://stackoverflow.com/questions/56862701

QUESTION

no connection pool with primary found

Asked 2019-Mar-22 at 15:41

I am using Rails and am experiencing a connection pool error very randomly and it does not target any single endpoint specifically. I can hit endpoints about 70% of the time without getting this error. The database is PostgreSQL running on Google Cloud. Here's the main stuff of the error I'm getting:

...

ANSWER

Answered 2019-Mar-22 at 15:41

First: gem uninstall sqlite then in gemfile change it for:

gem 'sqlite3', '~> 1.3.6' bundle install

rake db:migrate and restart server

Should works :)

Source https://stackoverflow.com/questions/52106397

QUESTION

Fog-google doesn't find credentials

Asked 2019-Feb-04 at 18:14

I have a Rails 5 application with Carrierwave. I would like to use fog-google gem but I cannot set it up because fog cannot retrieve the credentials.

I created a .fog file in my application root populated this way:

...

ANSWER

Answered 2017-Apr-11 at 14:00

QUICK SOLUTION

Put the .fog file in the root of the server (or your computer), not the one of the app.

This is pretty bad, but it's the first I found while quickly looking to solve the problem.

RIGHT SOLUTION

If you use google_json_key_location: google-storage-cdn.json Rails will look into / folder of the current server (your computer if you are working locally). In order to look into the application folder you need to use a Rails helper.

Source https://stackoverflow.com/questions/42403597

QUESTION

Excon::Error::Socket: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A (OpenSSL::SSL::SSLError)

Asked 2018-May-03 at 09:29

I'm attempting to use fog-google to upload images to my google cloud storage. My code looks like this:

...

ANSWER

Answered 2017-Nov-16 at 20:27

It's because you are trying to reach a url https and is failing to verify ssl in your case.

Try adding OpenSSL::SSL::VERIFY_PEER = OpenSSL::SSL::VERIFY_NONE

Edit - For Your concern about Man In The Middle Attack

Also You can verify your application by adding an ssl certificate with the following steps

Download https://curl.haxx.se/ca/cacert.pem into a path_to_file\cacert.pem. Make sure you save it as a .pem file, rather than a text file.
Set Environment Variable: SSL_CERT_FILE = path_to_file\cacert.pem
Restart all your ruby / rails applications and the retry accessing it now.

Source https://stackoverflow.com/questions/47337644

QUESTION

Why does Bundler refuse to accept a gem with no version specified?

Asked 2018-Mar-20 at 23:15

The command:

...

ANSWER

Answered 2018-Mar-20 at 23:15

After a day and a half of single-stepping through Bundler, I have arrived at an answer:

If both of the following things happen:

Bundler looks at a conflicting version of a package (such as librato-metrics) before finding the right version.
Another error of any kind happens, either before or after #1.

...Bundler will show the resolved conflict error along with all the other errors, even though the conflict was actually resolved and doesn't need to be addressed.

Source https://stackoverflow.com/questions/49372891

QUESTION

All tests throwing TypeError: no implicit conversion of nil into String

Asked 2018-Feb-12 at 20:13

UPDATE 20180209: I created a new dummy app with what comes with the initial Rails 5.1.4 install (which includes minitest 5.11.3) and tests completed without issue. Going to continue to experiment with the gemfile to see if I can't narrow down what in the world may be causing this problem...

If you have any ideas or pointers, please let me know!

I recently started testing a new portion of my codebase and I've discovered a very critical issue. For whatever reason, every test is now throwing the titled error. Looking into the trace, it looks like for some reason the quoted name/title of my tests is causing a problem. Going back and running tests that I know were passing (though admittedly on earlier gem versions) unfortunately yields the same results, as shown below with the User model.

I've tried everything I know to do, including completely removing and reinstalling RVM, Rails, and Ruby. I've even tried versioning Minitest to an earlier build, like 10.5.3, but still no luck. I've spent most of the day trying to fix this; I'm at my wits end and desperately need help! Though I've learned the hard way that I now need to explicitly version protect ALL of my gems ;)

Thank you in advance! Please let me know if you need me to include any more files/snippets. I'll do my best to reply to any questions as my schedule allows, hopefully within 24 hours.

Returned trace:

E

Error: UserTest#test_should_be_valid: TypeError: no implicit conversion of nil into String

/home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/railties-5.1.4/lib/rails/test_unit/reporter.rb:70:in method': undefined methodtest_should_be_valid' for class Minitest::Result' (NameError) from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/railties-5.1.4/lib/rails/test_unit/reporter.rb:70:informat_rerun_snippet' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/railties-5.1.4/lib/rails/test_unit/reporter.rb:23:in record' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:803:inblock in record' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:802:in each' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:802:inrecord' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:334:in run_one_method' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:321:inblock (2 levels) in run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:320:in each' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:320:inblock in run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:360:in on_signal' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:347:inwith_info_handler' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:319:in run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/railties-5.1.4/lib/rails/test_unit/line_filtering.rb:9:inrun' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:159:in block in __run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:159:inmap' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:159:in __run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:136:inrun' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/minitest-5.11.3/lib/minitest.rb:63:in block in autorun' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application.rb:171:infork' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application.rb:171:in serve' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application.rb:141:inblock in run' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application.rb:135:in loop' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application.rb:135:inrun' from /home/blake/.rvm/gems/ruby-2.4.1@land_app/gems/spring-2.0.2/lib/spring/application/boot.rb:19:in ' from /home/blake/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:inrequire' from /home/blake/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require' from -e:1:in'

This is from a fairly standard User model test that has not raised issues before...

user.rb

...

ANSWER

Answered 2018-Feb-12 at 20:13

Got this sorted out by reverting to an earlier commit when things were working as expected, and pulled in needed updates through a $ git checkout approach.

If I had to guess I think the problem I was having may have had something to do with my intervening update to 2.5.0 through RVM, which introduced more headaches than it was worth (not Rails's fault, or even RVM's since 2.5.0 isn't yet officially supported by RVM).

Source https://stackoverflow.com/questions/48698622

QUESTION

Upgrade kaminari to 1.0.1 using rails admin and active_support

Asked 2017-Oct-04 at 11:39

I want to update my dependencies, it works if I specify the kaminari version to be 0.17.0

But now with this version of kaminari i can't make rails_admin work anymore, see here the error I got => https://github.com/sferik/rails_admin/issues/2939

When I don't specify a version of kaminari i get this error =>

...

ANSWER

Answered 2017-Oct-04 at 11:39

I solved this issue by also upgrading mongoid dependecies.

Apparently, Kaminari 1.0.1 is not compatible with mongoid-audit 1.0.2

Source https://stackoverflow.com/questions/46563499

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fog-google

Add the following two lines to your application's Gemfile:.
Follow the instructions to generate a private key. A sample credentials file can be found in .fog.example in this directory:. 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.
Once you've specified your credentials, you should be good to go!.

Support

Fog-google is currently supported on Ruby 2.6+. 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.

Find more information at: