Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
sk593 opened this issue Mar 29, 2024 · 0 comments
Open

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

sk593 opened this issue Mar 29, 2024 · 0 comments
Labels
triaged

Comments

@sk593
Copy link
Contributor

sk593 commented Mar 29, 2024 •
edited by willtsai
Loading

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sylvainsf @sk593