Semantic Versioning Specification
That's regular Semantic Versioning
> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
> Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
> If your software is being used in production, it should probably already be 1.0.0.
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
But hey… even terraform made it to v1.0.0 after some time… https://github.com/hashicorp/terraform/releases/tag/v1.0.0
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
Vim-fork focused on extensibility and usability
Neovim is listed as a "notable ZeroVer project" and yet it has a 1.0(!!) milestone in the GitHub project page.
Deploy Kubernetes Helm Charts
Helmfile might be a good addition to the list: https://github.com/roboll/helmfile
Daemon to ban hosts that cause multiple authentication errors
Terraform provider for Azure Active Directory
We have an internal provider that handles generation of IAM Roles and IAM users via an external API for various security reasons I may or may not agree with. The constant provider changes in 0.10 and upward were extremely painful. We actually ended up having several teams who so hopelessly fubared their tfstates trying to skip minor releases, we ended up having to take it away and put together a task force to do it ourselves across almost 200 repositories.
I’m not sure what you mean by “all three major cloud providers rewrote their own APIs.” Azure, AWS, and Google are all maintained by Hashicorp. In fact, if you peruse the issues you’ll often see PRs opened by employees of the respective providers trying to fix blocking issues and they often devolve into literal begging for Hashicorp to respond and at least tell them why something hasn’t been merged. I know one blocker actually cost Azure a very substantial customer as it languished in Hashicorp’s queue.
Hashicorp’s constant refrain of “Well it’s a 0 version software” while selling enterprise support and constantly shilling their wares as production ready across the entire DevOps space was dishonest.
I appreciate the position they were in and I appreciate even more their attempt to at least put out a good PR move with their 1.0 release. We will see how well it holds up over the years.
Also I pretty clearly said there isn’t much options. What you call “that good” I call “better than everything else but still byzantine and hellish to deal with every time someone DMs me, ‘hey, you know terraform right?’”
Terraform provider for Azure Resource Manager
OPS - Build and Run Open Source Unikernels. Quickly and easily build and deploy open source unikernels in tens of seconds. Deploy in any language to any cloud.
Terraform AWS provider
Terraform Google Cloud Platform provider
azurerm provider for Azure
2 projects | reddit.com/r/Terraform | 23 Jan 2022
Azure provider - workaround to define a stored access policy for a service SAS?
1 project | reddit.com/r/Terraform | 5 Nov 2021
Unsupported Block error for global_parameter in Azure data factory
1 project | reddit.com/r/Terraform | 4 Nov 2021
What's the best way to deal with config drift from GUI usage?
1 project | reddit.com/r/devops | 31 Oct 2021
Building a Secure CI/CD Integration with Azure
1 project | dev.to | 21 Oct 2021