-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
generate_presigned_url docs missing links and explanations #3670
Comments
HI @mdavis-xyz, thanks for reaching out. This documentation has a lot more details than the reference guide, so it'd recommend checking that out, but I'll go over your questions here as well.
The reason that Here's an example provided in the aforementioned documentation.
ClientMethod is the operation you want your url to execute. You can use
Yes, those parameters go in Params as a dictionary, where the name of the parameter is a key, and the desired value for that parameter is a value. The correct format for each key can be found on the reference guide page for the ClientMethod you've chosen.
You are correct, this parameter refers to the HTTP method, including 'GET', 'PUT', and 'POST. You don't typically need to specify this, since it defaults to the correct method for the ClientMethod you've specified. I hope that answers all your questions. Regarding improvements to the documentation, do you think that adding an example to the reference guide like the one I posted would be helpful? |
The documentation you linked to makes it sound like this is just a normal API operation.
Yes, but I think it would be more helpful to just document each argument to the same level that is done for other calls.
|
While I wait to hear back about improving the reference guide, I do want to mention a much more detailed piece of documentation that I didn't link in my original reply. I hope that clears up a bit of confusion in the meantime. |
Just checking, who are you waiting on about improving the reference guide? I responded with improvement suggestions in my last comment. You're not waiting on me, right? That detailed doc is more helpful. Although still not comprehensive enough. But it would be worth linking from here to here. I still don't see how I can specify something like version id. Is the What about fields like One of the things I don't get is how to know what HTTP method to use. That last link says that the SDK will figure it out based on the non-HTTP method. But I need to tell the unauthorised client what method to use to access the pre-signed url after it's been generated. e.g. it says you can do presigned urls for |
Closing in favor of a more recent duplicate issue : #3901 |
|
@RyanFitzSimmonsAK any update on actually implementing the useful suggestions that @mdavis-xyz spelled out about documenting exactly what values are allowed for each of these parameters somewhere like https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/generate_presigned_url.html? |
Describe the issue
For most boto functions, each documentation page has something like:
e.g. s3.delete_object.
But for S3 generate_presigned_url it doesn't have a link to the raw API documentation.
Also, most parameters aren't completely defined.
ClientMethod
. What's that? Is thatget
,Get
,GET
, or something else?Params
- what is the meaning of this?HttpMethod
- hang on, this sounds the same asClientMethod
. Is this theGET
part? (Orget
, orGet
). Or is thishttps
vshttp
?Params
? If so, is itBucket
orBucketName
, or a path likes3://bucket/path/file.txt
?Usually when the boto docs are ambiguous in this way (e.g. missing possible enum values) I just click on the link to the raw API documentation. But that link is omitted.
I'm not able to even figure out where that link should point to. It seems this API call is not documented by AWS?
#3048 was related, but expired due to staleness.
Links
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3/client/generate_presigned_url.html
The text was updated successfully, but these errors were encountered: