describe_cluster method of EMR client not returning field 'Code'

[albertoCCz]

Describe the bug

describe_cluster method of EMR client not returning field Code.

Expected Behavior

When executing a describe_cluster, and according to documentation, the field Code should exist under Cluster > Status > StateChangeReason:

{
    'Cluster': {
        'Id': 'string',
        'Name': 'string',
        'Status': {
            'State': 'STARTING'|'BOOTSTRAPPING'|'RUNNING'|'WAITING'|'TERMINATING'|'TERMINATED'|'TERMINATED_WITH_ERRORS',
            'StateChangeReason': {
                'Code': 'INTERNAL_ERROR'|'VALIDATION_ERROR'|'INSTANCE_FAILURE'|'INSTANCE_FLEET_TIMEOUT'|'BOOTSTRAP_FAILURE'|'USER_REQUEST'|'STEP_FAILURE'|'ALL_STEPS_COMPLETED',
                'Message': 'string'
            },
...
        }
    }
}

Current Behavior

The field Code is not present in the response of describe_cluster.

Reproduction Steps

from pprint import PrettyPrinter
import boto3

pp = PrettyPrinter(indent=4, sort_dicts=False, depth=10)

emr_client = boto3.Session(profile_name=<profile_name>).client('emr')
emr_res = emr_client.describe_cluster(ClusterId=<cluster_id>)
pp.pprint(emr_res)

Possible Solution

No response

Additional Information/Context

No response

SDK version used

boto3-1.33.6

Environment details (OS name and version, etc.)

MacBook Pro - macOS Ventura 13.6.2 - Apple Chip M1 Pro

[albertoCCz]

Hey @RyanFitzSimmonsAK, if you'd need more info to investigate this, let me know :)

[RyanFitzSimmonsAK]

Hi @albertoCCz, thanks for your patience. I was able to reproduce this behavior. Boto3 returns the response provided by the service team, so I've reached out to the EMR team about this issue. In the meantime, as this is a service team issue, I'm going to create a tracking issue in our cross-SDK repository (aws/aws-sdk#664). Please refer to that issue for any updates. Thanks!

[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.