Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Fix Storage naming to (mostly) match API Schema #544

Copy link
Copy link
@silvolu

Description

@silvolu
Issue body actions

(Above added by @dhermes on 1/19/2014)


The naming conventions appear to be modeled around s3's boto library, but the library is not compatible with S3. It seems like it might be more useful to use the JSON API resource names.
The major difference here is the use of "key" to represent an "object" resource. The Cloud Storage API JSON docs typically use the word "key" to refer to an API key or a service account private key file, never to a cloud object resource. Of course "object" is a reserved name in Python, but there are other possibilities.
With the hierarchy of connection/bucket/key, this looks a lot like boto without actually supporting s3, which could confuse users.

/cc @thobrla

Metadata

Metadata

Assignees

Labels

api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.type: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.