Add ability to use Service Accounts with Google Cloud Storage API

Bug #1652250 reported by az
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

this is a forward of debian bug 848943, which lives over there: http://bugs.debian.org/848943

the original reporter requests that duplicity should support Google Cloud credentials (Service Accounts) for google storage.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 1652250] [NEW] Add ability to use Service Accounts with Google Cloud Storage API

The fix for this is in the trunk now and will be released with 0.7.11 in
the next day or so.

On Fri, Dec 23, 2016 at 2:51 AM, az <email address hidden> wrote:

> Public bug reported:
>
> this is a forward of debian bug 848943, which lives over there:
> http://bugs.debian.org/848943
>
> the original reporter requests that duplicity should support Google
> Cloud credentials (Service Accounts) for google storage.
>
> ** Affects: duplicity
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1652250
>
> Title:
> Add ability to use Service Accounts with Google Cloud Storage API
>
> Status in Duplicity:
> New
>
> Bug description:
> this is a forward of debian bug 848943, which lives over there:
> http://bugs.debian.org/848943
>
> the original reporter requests that duplicity should support Google
> Cloud credentials (Service Accounts) for google storage.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1652250/+subscriptions
>

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.7.11
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
Revision history for this message
Daniel Miranda (danielkza2) wrote :

Sorry to resurrect this issue after a long time, but I can't find any mention on how to use service accounts in the documentation, or the corresponding changes in the code. AFAIK `boto` is still used, which only supports the S3-style HMAC keys, while service accounts require OAUth2 authentication. Am I missing something obvious?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.