terraform-provider-docker
terraform-website
| terraform-provider-docker | terraform-website | |
|---|---|---|
| 1 | 2 | |
| 135 | 163 | |
| - | - | |
| 10.0 | 8.7 | |
| over 3 years ago | 10 months ago | |
| Go | JavaScript | |
| Mozilla Public License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
terraform-provider-docker
-
Maintaining the terraform provider for docker
We all use open source projects to develop, run and evolve the software that we use both internally and at the clients who pay us for our expertise and experience. We find bugs, see the need to extend the functionality or stumble over a piece of documentation that is not fully clear and understandable. We know talented folks took precious time to design, create, maintain and evolve such open-source projects. As we are working on those projects heavily, we carve out time to make a contribution by creating bug reports and providing fixes for them; and if we see the need for a new feature, try our best to provide it. In our case, we wanted to deploy docker services into a docker swarm via terraform. As those resources were not supported at that time in 2018, we filed a colossal pull request, which led us to important learnings. We will talk about them later in detail in this post. First, let's explain how it evolved that we started maintaining this terraform provider.
terraform-website
-
Maintaining the terraform provider for docker
In 2017, after the provider-split in terraform 0.10, the docker provider was more or less abandoned and not actively maintained. We started contributing small features and bug fixes so we could use them in our deployment pipelines. We got in touch with several core contributors and began asking questions about the internals, especially about extending terraform, and how to write providers correctly. At that time, the documentation was still a work in progress, and for edge cases, there were no examples in the documentation yet. We started filing pull requests to update the documentation for this.
-
Can Terraform documentation be "more UI friendly" = )
I'd create the issue here: https://github.com/hashicorp/terraform-website
What are some alternatives?
terraform-plugin-sdk - Terraform Plugin SDK enables building plugins (providers) to manage any service providers or custom in-house solutions
former2 - Generate CloudFormation / Terraform / Troposphere templates from your existing AWS resources.
terraform-provider-docker - Terraform Docker provider
kubernetes-cluster-setup-using-terraform-and-k3s-on-digitalocean - Demonstration of how you can use set up your Kubernetes cluster on DigitalOcean using Terraform + k3s + Ansible
git-chglog - CHANGELOG generator implemented in Go (Golang).
generator-tf-module - Project scaffolding for Terraform
devops-exercises - Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions
terradiff - Get told when your Terraform config doesn't match reality
terraform-provider-aws - The AWS Provider enables Terraform to manage AWS resources.
cf-to-tf - CLI tool for generating Terraform configuration and state for existing CloudFormation resources