There are a growing number of repositories for AWS provider implementions, generally by service. There should be a place to see a list of all of those repositories. Without this, it will be hard for customers to influence the design and implementation of these providers.
Here's the current list that I'm aware of:
We've assigned them all topics, so you can filter the organization repos by aws-resources; https://github.com/search?q=topic%3Aaws-resources+org%3Aaws-cloudformation&type=Repositories
Awesome! How will new users discover this?
We're thinking about something like https://pages.github.com/ for these sorts of docs as there's not a natural landing page in the repos itself.
I've been using https://github.com/aws-cloudformation?q=aws-cloudformation-resource-providers-&type=public
have been looking for ways to more easily work with all of them though. Much easier if all providers were in one repo
I've added the third party types to the awesomelist repo - do you guys want us to add them there for now?
Following up here - do you want me to put your list in the awesomelist repo? I can also create a separate page there too
I have updated the issue with all the current repos using @PatMyron's search method, which matches repos of the form aws-cloudformation/aws-cloudfomration-resource-providers-*. I should note that @rjlohan's method, repos under aws-cloudformation with the topic aws-resources already misses out ACM PCA and Event Schemas, which have no topics.
Why wouldn't this list of official CloudFormation types be in the AWS CloudFormation docs proper? Why wouldn't the repo be linked from the CloudFormation resource type reference itself?
Added 16 more repos. Still shouldn't need a customer to maintain this information.
Added 7 more repos. Still an embarrassment that a customer is maintaining this information.
Added 9 more repos. Still an embarrassment that a customer is maintaining this information.
Most helpful comment
I've been using https://github.com/aws-cloudformation?q=aws-cloudformation-resource-providers-&type=public
have been looking for ways to more easily work with all of them though. Much easier if all providers were in one repo