Skip to content

Add per-service CLI flags for client context params#10166

Open
AndrewAsseily wants to merge 3 commits intov2from
client-context-params
Open

Add per-service CLI flags for client context params#10166
AndrewAsseily wants to merge 3 commits intov2from
client-context-params

Conversation

@AndrewAsseily
Copy link
Copy Markdown
Contributor

Issue #, if available: N/A

Description of changes:

This exposes clientContextParams from the service model as per-service CLI flags. Currently that's S3 (5 params) and S3Control (1 param). The existing s3 config values still take priority.
Added model validation tests for name collisions between client context params and operation input members, and for unsupported param types (currently only string and boolean are supported).

Changelog type: I used enhancement since the underlying plumbing already exists in and this is just surfacing it in the CLI.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@AndrewAsseily AndrewAsseily marked this pull request as ready for review March 27, 2026 14:24
Copy link
Copy Markdown
Member

@ashovlin ashovlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't done a full pass on the code yet, but stepping through this in a debugger I am NOT seeing the new parameters influencing the endpoint rules with a breakpoint at EndpointProvider->resolve_endpoint.

aws s3api list-objects-v2 --bucket <mrap arn> --disable-multi-region-access-points is still working for me.

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

Successfully merging this pull request may close these issues.

2 participants