terraform-module-template
semver
terraform-module-template | semver | |
---|---|---|
6 | 726 | |
71 | 7,037 | |
- | 0.8% | |
6.1 | 0.6 | |
6 days ago | 16 days ago | |
Go | ||
Apache License 2.0 | - |
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-module-template
-
Treating your terraform code "as an app". Favouring inputs over code changes. I wish I saw more like this in places I worked at.
You should not use multiple optional inputs, at least not if those are going to be used to decide to create optional resources. Instead you should favor composition of modules. An example of composition using "Higher order modules" can be found here https://github.com/DontShaveTheYak/terraform-module-template
-
Most common devOps tasks?
Yeah I do. I'm actually the author of the https://github.com/DontShaveTheYak/terraform-module-template That sets up all those tools for you.
-
Terraform Module Template
A higher-order module is just a module that calls another module to extend that modules functionality. You can see it being used here https://github.com/DontShaveTheYak/terraform-module-template/tree/main/modules/greet_multiple
-
This is the best way to create a Terraform module!
My latest project is https://github.com/DontShaveTheYak/terraform-module-template
- Show HN: Terraform module template with pre-configured CICD
semver
-
The right development flow: Better than Agile
We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-releaseβ¦
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
What are some alternatives?
terraform-aws-vpc - Terraform module to create AWS VPC resources πΊπ¦
react-native - A framework for building native applications using React
personal-zero-trust-hashicorp-vault - Cloudflare for Teams + HashiCorp Vault = Zero Trust Love
semantic-release - :package::rocket: Fully automated version management and package publishing
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources πΊπ¦
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
terraform-docs - Generate documentation from Terraform modules in various output formats
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
tflint - A Pluggable Terraform Linter
helmfile - Deploy Kubernetes Helm Charts
terraform-layout-example - Example of a Truss Terraform project
Poetry - Python packaging and dependency management made easy