Skip to content

Missing AWS data that doesn't follow SchemaDefinition format  #38

@sk593

Description

@sk593

There are quite a few instances where an AWS definition doesn't match the SchemaDefinition format and does not get added as a type during generation. Examples here with AutomationRule_arnOrId, StringFilterComparison, Tags even though they're defined in the AWS data

These cases should be documented as part of the type definitions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions