DetailsDocument does not exist in DescribeEntityOutput

[YasuhiroTakahashi]

Describe the bug

The recently added response item "Details Document" does not exist in DescribeEntityOutput.
https://docs.aws.amazon.com/marketplace-catalog/latest/api-reference/API_DescribeEntity.html#API_DescribeEntity_ResponseSyntax

Expected Behavior

We expect DetailsDocument to be added to DescribeEntity.

Current Behavior

The following error occurred

SerializationError: failed to unmarshal response error
    status code: 502, request id: xxxxxxxxxxx

Reproduction Steps

Below are the parts where the SDK is used.

func (s service) DescribeEntityByProductCode(ctx context.Context, settings *setting.Settings) (*catalog.Entity, error) {
	client, err := s.ConnectCatalogService(ctx, settings)
	if err != nil {
		return nil, err
	}

	res, err := client.DescribeEntityWithContext(ctx, &marketplacecatalog.DescribeEntityInput{
		Catalog:  aws.String(catalogName),
		EntityId: aws.String(settings.ProductCode.String()),
	})

	if err != nil {
		return nil, errlib.Errorf(codes.Internal, "aws marketplace error: %v", err)
	}
	if res.Details == nil {
		return nil, errlib.ErrorfWithMessage(codes.Internal, "entity details is nil")
	}

	return newEntity(res.Details)
}

Possible Solution

We would like the following types to be modified.

aws-sdk-go/service/marketplacecatalog/api.go

Line 2172 in 0ba8f0f

type DescribeEntityOutput struct {

Additional Information/Context

No response

SDK version used

v1.43.29

Environment details (Version of Go (go version)? OS name and version, etc.)

go version go1.21.3 linux/amd64

[RanVaknin]

Hi @YasuhiroTakahashi ,

I can confirm that that field is missing. Perhaps the codegen failed because v2 has that field. We are looking into it.
Thanks,
Ran~

[lucix-aws]

It's missing in this SDK simply because the c2j version of the model does not have that field. Conversely the smithy version of the model does, therefore it's present in v2.

I haven't checked a raw response but since they indicate that both versions exist in their docs it's worth upstreaming with the service team.

[lucix-aws]

See #5070. We have stopped supporting fields of this type in the v1 SDK due to them being broken across services. You will need to upgrade to SDK v2 to be able to read the field.

[github-actions]

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