release-drafter
tfsec
release-drafter | tfsec | |
---|---|---|
10 | 7 | |
3,207 | 2,991 | |
1.0% | - | |
4.8 | 9.4 | |
6 days ago | almost 3 years ago | |
JavaScript | Go | |
ISC License | MIT License |
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.
release-drafter
-
Auto Publish/Release - GitHub Actions
For releasing or publishing our code automatically, we will use the action Release Drafter
- Have some Git & GitHub "best practice" questions...
-
Feather’s ultimate guide to development: tips, tricks and best practices
New release drafts are triggered after every commit is pushed to the main staging build. The drafted release (built with release drafter) will contain all the commits added since the previous release and a suggested new version which will follow the Semantic Versioning rules.
-
How to do proper CI/CD with artifact promotion with GitHub Actions.
I am thinking I would have to create a GitHub release manually and then have a workflow listening on the "Release created" event, which would pull the image with the correct commit sha, tag it with the proper version and push it. Or using something like Release Drafter with a PR-based Git flow.
- Use Github Release Tag Name as Version in Cargo.toml?
-
Cookietemple: A cookiecutter based project creation tool
During 2021, we worked hard to improve it furthermore and add new functionality. We just released the latest version of cookietemple. It now includes (beside other templates for example an advanced C++ template or a Java CLI template) a modern python template using poetry, nox (nox-poetry), automatic docs setup as well as many cool and modern GitHub actions, like ReleaseDrafter (https://github.com/release-drafter/release-drafter).
-
Deploying our code at Feather
Every commit pushed to the main branch will trigger a staging build. In addition to this, every commit pushed to the main branch will draft a new release on GitHub with the help of the release drafter.
-
Automating updates from Upstream Source images
We are always actively working on the configuration for Renovate and will continue to fine-tune it. Having pull requests created for every upstream version change will also optimise the generation of automated changelogs (using the excellent Release Drafter GitHub Action we were already using on Lagoon).
-
How FirstPort manage GitHub, using code stored in GitHub
I wanted to provide a way to be able to easily create release notes, to enhance transparency on what we are delivering. I chose to use a tool called Release Drafter in our workflow. I wanted to configure how labels would be used in every repository, and for that, we standardised all labels across all repositories. I use: docs, dependencies, bug, feature, and maintenance.
-
Generate semantic-release with GitHub Actions
release-drafter / release-drafter
tfsec
-
Terraform in AWS
Using pre-commit framework with terraform repository, will help your code to be kept clean, formated, updated document and checked for tf security issues (optional with tfsec) before committing and pushing the code to git source.
-
Terraforming in 2021 – new features, testing and compliance
Here again more than one tool exists to assist. We will highlight two of the most popular ones here: tfsec and checkov. Both provide a predefined set of checks that they use to inspect your code, allowing to explicitly open exceptions (if you really want to) by annotating your code with comments, and adjust the configuration to ignore some modules, for example.
-
How FirstPort manage GitHub, using code stored in GitHub
An additional benefit of using a CI workflow is adding automated tests. In this scenario, I’ve added a step leveraging tfsec to scan for static code vulnerabilities. In the example below, tfsec warns against creating an Azure network security rule which is fully open. This will halt and fail the workflow unless I provide an ignore comment to accept the warning.
-
Terraform v15.0 with AWS (EKS deployment)
· Provision an EKS Cluster (AWS) · Terraform v15.0 · Terraform Registry · Pre-Commit · Terraform Pre-commit · Terraform-docs · Tflint · Tfsec
-
A way to restrict options for devs in AWS
Using terraform, create a skeleton directory that they can review for how EC2 instances should be created. Use tools like https://github.com/tfsec/tfsec or other scanners/linters to validate that your developers followed this process and didn't uncheck something.
-
Terraform VMware vSphere Provider - is it worth it?
I know tfsec (https://github.com/tfsec/tfsec) which is pretty good for AWS resources but I think vSphere resources are not implemented.
-
Gopher Gold #15 - Wed Oct 14 2020
tfsec/tfsec (Go): 🔒🌍 Static analysis powered security scanner for your terraform code
What are some alternatives?
semantic-release - :package::rocket: Fully automated version management and package publishing
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
probot - 🤖 A framework for building GitHub Apps to automate and improve your workflow
tflint - A Pluggable Terraform Linter
semver - Semantic Versioning Specification
terrascan - Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.
cookietemple - A collection of best practice cookiecutter templates for all domains and languages with extensive Github support ⛺
atlantis - Terraform Pull Request Automation
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
pre-commit-hooks - Some out-of-the-box hooks for pre-commit
SimpleLogin - The SimpleLogin back-end and web app
terraform-aws-gitlab-runner - Terraform module for AWS GitLab runners on ec2 (spot) instances