aws-sdk-go-v2

aws-sdk-go-v2 copied to clipboard

Describe the bug

I am creating batch operation jobs using S3Control CreateJob function. I have the ConfirmationRequired flag set to false in my job input.

Expected Behavior

The created job going into READY state.

Current Behavior

The create job goes into SUSPENDED state.

Reproduction Steps

Create a job input for a batch operation using s3control.CreateJobInput, setting ConfirmationRequired: false Then call s3control.CreateJob on the input Check the status of the newly created job in the console

Possible Solution

I believe the problem is because the generated serialiser only writes the tag out if it's set to true. In the documentation and API it's written that this flag isn't required, so it should default to false if not specified. However, would it be possible that the service doesn't handle this correctly and instead it sets the flag to true?

Additional Information/Context

No response

AWS Go SDK V2 Module Versions Used

github.com/aws/aws-sdk-go-v2/service/s3control v1.21.10

Compiler and Version used

go version go1.18.3 darwin/arm64

Operating System and version

MacOS 12.5.1

Hi @ioanamihailescu8 ,

We have an internal ticket cut for this exact issue (issue V691096268) @jasdel said:

This is an issue with S3Control’s service not adhering to the API model they defined. e.g. the ConfirmationRequired member is being treated as nullable (aka boxed), but is modeled as non-nullable (aka unboxed).

Since this is a service related issue, we can't fix anything on our end. I will update you once the issue is fixed on the service side.

Thanks. Ran~

Moving this issue back to the v2 SDK's repository. The API model for the member decorates the member as boxed (aka nullable) so it should of been generated as a pointer. This looks to be a bug in the SDK's code generation with regard to how this trait is being used.

OBE - ConfirmationRequired is correctly represented as *bool in the latest version.

⚠️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.