SQS ReceiveMessageInput.MessageSystemAttributeName missing on version 1.20 ^ about aws-sdk-go-v2 HOT 5 CLOSED

I see so for now to solve these problems for now just use the AttributeNames right? back to the old ways?

Thank's for answering

from aws-sdk-go-v2.

Hi @hryer ,

I just reached out to the SQS team and it seems like they are going to deploy the changes in the near future. In the meantime you can safely use AttributeNames.
Since this issue is a duplicate, I'm going to close it in favor of tracking it here.

Thanks again,
Ran~

from aws-sdk-go-v2.

@RanVaknin Hi sorry to bother, any updates about this issues?

If you don't mind, I'll add PR to solve this.

from aws-sdk-go-v2.

Hi @hryer ,

This is likely related to
aws/aws-sdk#623
aws/aws-sdk-js-v3#5403

and is not something we can solve on the SDK. This is likely due to a modeling issue with the SQS API model itself.

@RanVaknin Hi sorry to bother, any updates about this issues?

If you don't mind, I'll add PR to solve this.

This is not something you can fix through the SDK. If you look at the top of the file you mentioned it says the following

// Code generated by smithy-go-codegen DO NOT EDIT.

Indicating that this is code generated from the API model and has to be solved upstream.

Im going to reach out to the SQS team again to see if we can get their attention on this.
Thanks,
Ran~

from aws-sdk-go-v2.

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

from aws-sdk-go-v2.