You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd be open to having a community page on the website that lists not only providers but other Terraform related tooling that the community has created. If we want to use this issue as a way to collect those things I can add that page sometime.
mrjcleaver
changed the title
Registry for new (unofficial) providers
Website page(s) for community-related tooling such as unofficial providers
Aug 31, 2016
We don't have a page for capturing community tools in general, but we also don't really have the resources right now to manage one, so we're going to close this out.
Fortunately, in the time since this issue was created there has emerged a convention for curated lists of tools and libraries for an application to be named "Awesome ...", and so you can find many such lists maintained by third-parties by searching for "awesome terraform" on your favorite search engine. We're very grateful to the maintainers of those lists for taking the time to curate those resources.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Aug 19, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Re: #8518 I was surprised that providers not supported by Hashicorp are not listed at all.
History shows this leads us to duplication, wasted effort, disappointment and slower speed to market.
How about on the Providers page have a link to a wiki or similar so people can share what:
Then others can pitch in.
I assume this doesn't exist as it wasn't mentioned in the answer to 8518.
Thanks,
Martin.
The text was updated successfully, but these errors were encountered: