Nikolaus, I believe that our usage could leverage whatever S3QL supports, but we do currently use the gs legacy API keys with s3ql v1.17 (i.e. https://code.google.com/apis/console/#project:467632721924:storage:legacy). The issue for us would be migrating existing users from the legacy API to OAuth2 without disrupting their access to a given bucket. If that is clearly documented and not too difficult, we could manage the transition.
For s3ql usage, would OAuth2 change the tag from 'gs' to 'gs2', as was done with swift? I would be a little concerned if the logic changed for 'gs' to mean something else from version to version. Andy On Sun, Feb 1, 2015 at 4:43 PM, Nikolaus Rath <[email protected]> wrote: > Hello, > > Does anyone depend on using API / old-style authentication for accessing > Google Storage with S3QL? > > I am considering to make OAuth2 the only supported authentication method > for Google Storage. > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« > > -- > You received this message because you are subscribed to the Google Groups > "s3ql" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
