You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm using a local endpoint and I noticed that when I use the actions IAM list-users and list-access-keys the argument max-items is passing to the CLI but it doesn't parse it in the request body.
Expected Behavior
I would expect to see the max-items in the request body params.
Current Behavior
I don't see the max-items in the request body (as mentioned I can see it passed as argument).
Reproduction Steps
iam list-users s3-nc-user-1-iam iam list-users --path-prefix /abc/ --max-items 7 --debug
I added the --path-prefix flag to see a flag that passes (and a flag --max-items I think doesn't pass).
(s3-nc-user-1-iam is an alias
for AWS_ACCESS_KEY_ID=<access-key> AWS_SECRET_ACCESS_KEY=<secret-key> aws --no-verify-ssl --endpoint-url https://localhost:7005).
In the debug I see AWS CLI list the argument of max-items:
The behavior you described is expected. The AWS CLI uses a paginate customization to provide consistent pagination across services. For example commands like sqs list-queues expects MaxResults in the API request, but --max-items will still be mapped to that via the CLI. You should see a line like this in your debug logs:
awscli.customizations.paginate - DEBUG - Modifying paging parameters for operation: ListUsers
tim-finnigan
added
closing-soon
This issue will automatically close in 4 days unless further comments are made.
pager
issues related to AWS_PAGER, cli_pager, or other client-side paging (not API pagination)
and removed
bug
This issue is a bug.
investigating
This issue is being investigated and/or work is in progress to resolve the issue.
needs-triage
This issue or PR still needs to be triaged.
labels
Jul 15, 2024
@tim-finnigan thank you for the comment.
I could see awscli.customizations.paginate - DEBUG - Modifying paging parameters for operation: ListUsers in the output.
As I understand it, to see the value of this parameter I need to add the flag --no-paginate, correct?
Describe the bug
Hello,
I'm using a local endpoint and I noticed that when I use the actions IAM
list-users
andlist-access-keys
the argumentmax-items
is passing to the CLI but it doesn't parse it in the request body.Expected Behavior
I would expect to see the
max-items
in the request body params.Current Behavior
I don't see the
max-items
in the request body (as mentioned I can see it passed as argument).Reproduction Steps
iam list-users
s3-nc-user-1-iam iam list-users --path-prefix /abc/ --max-items 7 --debug
I added the
--path-prefix
flag to see a flag that passes (and a flag--max-items
I think doesn't pass).(s3-nc-user-1-iam is an alias
for
AWS_ACCESS_KEY_ID=<access-key> AWS_SECRET_ACCESS_KEY=<secret-key> aws --no-verify-ssl --endpoint-url https://localhost:7005
).In the debug I see AWS CLI list the argument of max-items:
In the debug I don't see the max params passing to the request's body (
PathPrefix
we can see):iam list-access-keys
:s3-nc-user-1-iam iam list-access-keys --max-items 1 --user-name shira-1001 --debug
In the debug I see AWS CLI list the argument of max-items:
In the debug I don't see the max params passing to the request's body (
UserName
we can see):Possible Solution
You can parse the
max-items
and add it to the request body.Additional Information/Context
CLI version: aws-cli/2.17.11 Python/3.11.9 Darwin/23.4.0 source/arm64
CLI version used
2.17.11
Environment details (OS name and version, etc.)
MacOS 14.4.1
The text was updated successfully, but these errors were encountered: