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

Issues with Custom Storage location doc #782

Open
kelshmo opened this issue Jun 2, 2020 · 4 comments
Open

Issues with Custom Storage location doc #782

kelshmo opened this issue Jun 2, 2020 · 4 comments

Comments

@kelshmo
Copy link
Collaborator

kelshmo commented Jun 2, 2020

@kelshmo kelshmo self-assigned this Jun 2, 2020
@allaway
Copy link
Contributor

allaway commented Aug 13, 2020

Additional issues that I have run into:

-The docs state that an owner.txtfile is required for read-write access to a bucket, but from what I can tell this is also required to be able to link up a read-only bucket. Reorganizing this section would likely fix a lot of confusion (and would have saved me an hour of trying to figure out why I couldn't link up a read-only bucket)
-The docs do not describe how to retrieve the storageLocationId

@allaway
Copy link
Contributor

allaway commented Aug 13, 2020

-several snippets do not specify where the toJSON function is coming from. Should specify rjson::toJSON as JSON produced with jsonlite::toJSON without the auto_unbox = T parameter set will cause synapser to throw an error

@kelshmo kelshmo removed their assignment Aug 13, 2020
@allaway
Copy link
Contributor

allaway commented Aug 14, 2020

another issue: docs don't describe how to change a storage location programmatically. This is not as simple as re running the "https://docs.synapse.org/articles/custom_storage_location.html#set-s3-bucket-as-upload-location" snippet, because if an upload location already exists, synapse throws this error:

Error in value[3L] : 400 Client Error:
A project setting of type 'upload' for project syn11727056 already exists.

So there must be a need to remove the project setting but it's not clear how to do that.

@allaway
Copy link
Contributor

allaway commented Aug 14, 2020

Looking through the API docs, this is how I ended up removing the project setting so that I can add a new one:

projectSettingsId <- synRestGET(glue::glue('/projectSettings/{parentId}/type/upload'))$id
synRestDELETE(glue::glue("/projectSettings/{projectSettingsId}"))

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

No branches or pull requests

2 participants