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
max-keys option is undocumented for s3api list-object-versions #8592
Comments
Hi @iainelder, thanks for reaching out. There's a few different things going on here to result in this behavior. The AWS CLI documentation generally will hide service pagination parameters in favor of its own parameters ( As I'm sure you saw in the issues you linked, there's some weird behavior around operations with multiple paginatable keys. We do already have a backlog item to better document this behavior by clarifying which response element is affected by |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
Describe the issue
The list-object-versions documentation refers to max-keys in the descriptions of other options.
The max-keys option needs its own description and an example.
The max-items option is similar and so sometimes people come to GitHub to ask for how to make max-items act like max-keys.
Today those issues are the best documentation I can find for max-keys.
Links
The text was updated successfully, but these errors were encountered: