Skip to content
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

Adds JSON API support when using Google Storage #381

Merged
merged 1 commit into from
Mar 13, 2019

Conversation

mohangk
Copy link
Contributor

@mohangk mohangk commented Mar 10, 2019

The current Google Storage support requires the
use of the S3 compatible API on GCS which is
slower and not leveraging service accounts.
The underlying library Fog Google does support
the ability to use Google Storage JSON API
(https://github.com/fog/fog-google#storage)

This change adds support for the setting of the
relevant config options and passes these config
options to Fog Google so that we can use service
accounts.

The current Google Storage support requires the
use of the S3 compatible API on GCS which is
slower and not leveraging service accounts.
The underlying library Fog Google does support
the ability to use Google Storage JSON API
(https://github.com/fog/fog-google#storage)

This change adds support for the setting of the
relevant config options and passes these config
options to Fog Google so that we can use service
accounts.
@coveralls
Copy link

coveralls commented Mar 10, 2019

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

15 similar comments
@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

coveralls commented Mar 10, 2019

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

coveralls commented Mar 10, 2019

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

coveralls commented Mar 10, 2019

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@coveralls
Copy link

Pull Request Test Coverage Report for Build 308

  • 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+1.2%) to 61.835%

Totals Coverage Status
Change from base Build 307: 1.2%
Covered Lines: 337
Relevant Lines: 545

💛 - Coveralls

@reinoutdeclerck
Copy link

It would be great to also support 'google_json_key_string', to support environments where you can't store physical files unless you check them into the repo (Heroku)

@mohangk
Copy link
Contributor Author

mohangk commented Mar 11, 2019

@reinoutdeclerck - sure happy to add that once this PR lands.

@PikachuEXE
Copy link
Member

The change looks good for me...
But have you try this version yourself? I cannot test it since I use AWS...

@mohangk
Copy link
Contributor Author

mohangk commented Mar 12, 2019

Yes @PikachuEXE we are using this internally at our organisation.

@PikachuEXE PikachuEXE merged commit f880273 into AssetSync:master Mar 13, 2019
@PikachuEXE
Copy link
Member

Will release this on Friday or next week
Ping me if you think that I forget :)

@mohangk
Copy link
Contributor Author

mohangk commented Mar 14, 2019

Thanks @PikachuEXE

@PikachuEXE
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants