Skip to content

Conversation

@wangshu3000
Copy link

Issue #: #3637

Description of changes:

This PR is to fix a shorthand doc issue. The struct type in the map should be wrapped in curly braces {}.

Doc url: https://docs.aws.amazon.com/cli/latest/reference/sqs/send-message.html

Before the change:
KeyName1=DataType=string,StringValue=string,BinaryValue=blob

After the change:
KeyName1={DataType=string,StringValue=string,BinaryValue=blob}

@wangshu3000 wangshu3000 changed the base branch from v2 to develop December 13, 2022 00:39
@wangshu3000
Copy link
Author

Can anybody please have a review? Is this repo still open to external contribution? Thanks.

@brianwarner
Copy link

Hi @kdaily and @dlm6693, would it be possible to have a look at this?

@wangshu3000
Copy link
Author

Hi @tim-finnigan @kyleknap @kdaily

Would you please have a review on this PR? This it to fix the shorthand syntax issue in the cli doc. Both v1 and v2 all have this issue.

Thanks.

@Me042589
Copy link

Me042589 commented May 28, 2024 via email

@tim-finnigan
Copy link
Contributor

Thanks for creating this PR and for your patience here. Linking related issues/documentation:

So taking sqs send-message for example, the Shorthand Syntax in the documentation currently looks like:

image

And with your changes:

image

And that looks like the right format to use, for example this works for me:

aws sqs send-message --queue-url https://sqs.us-west-2.amazonaws.com/account-id/test --message-body TestBody --message-attributes "TenantID={StringValue=TestTenant,DataType=String},TenantName={StringValue=Bob,DataType=String}"

I brought this up for discussion with the team, and there were a couple more things that we wanted to look into prior to submitting a fix. For example, we want to test that the text still renders correctly when running aws sqs send-message help in different shells for example, which it looks like it does at least in macOS Terminal:

image

So from what I can tell these changes look good, but we may just need to verify in a couple more places prior to approving the PR.

@aemous
Copy link
Contributor

aemous commented Jan 26, 2026

Thank you for your submission. This PR has been superseded by #9982.

The issue is now already fixed as of versions 1.44.25 and 2.33.7. Closing PR.

@aemous aemous closed this Jan 26, 2026
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.

5 participants