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.

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

Publish AWS common definitions #374

Open
dpantke opened this issue Dec 23, 2019 · 5 comments
Open

Publish AWS common definitions #374

dpantke opened this issue Dec 23, 2019 · 5 comments
Assignees

Comments

@dpantke
Copy link

dpantke commented Dec 23, 2019

I noticed that in your examples, for AWS resources ( which you are using internally I'd imagine ), you have a common definition file for types that can be included for reference. The one I'm specifically referring to here is aws.common.types.v1.json . I would like that to be published at a well-known URL so that I can reference it to get easy reference when dealing with common parameters I want validated like availability zone, region, ARN, etc....

@rjlohan
Copy link
Contributor

rjlohan commented Dec 27, 2019

These schemas are planned to be published soon - probably in the next couple of weeks. Stay tuned.

@tobywf
Copy link
Contributor

tobywf commented Feb 12, 2020

I believe this is now available in some regions, for example: https://schema.cloudformation.us-east-1.amazonaws.com/aws.common.types.v1.json

@benkehoe
Copy link

Is there a root URL that makes these types discoverable?

@rjlohan
Copy link
Contributor

rjlohan commented Feb 12, 2020

Is there a root URL that makes these types discoverable?

Yeah this should be announced soon, once it's available in all regions is usually the process.

@PatMyron
Copy link
Contributor

PatMyron commented Apr 29, 2020

GovCloud partition is incorrect and isolated partitions are missing in the Arn definition

More partitions coming too, so let's just generalize beyond current partitions


AvailabilityZone definition does not match local zones or wavelength zones:

us-west-2-lax-1a
us-west-2-lax-1b
...


tried to start fixing here, but didn't propagate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants