setup-terraform
pipeline
setup-terraform | pipeline | |
---|---|---|
12 | 51 | |
1,279 | 8,294 | |
3.0% | 0.4% | |
8.0 | 9.7 | |
5 days ago | 3 days ago | |
JavaScript | Go | |
Mozilla Public License 2.0 | 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.
setup-terraform
-
Accelerating the Implementation of DevOps Culture in Your Organization with Amazon CodeCatalyst
# Adaptation of the https://developer.hashicorp.com/terraform/tutorials/automation/github-actions workflow Name: TerraformMainBranch SchemaVersion: "1.0" # Here we are including the trigger for this workflow: Push / Pull Request. If not included then this workflow will be executed only manually Triggers: - Type: Push Branches: - main # Here we are defining the actions that will be executed for this workflow Actions: Terraform-Main-Branch-Apply: Identifier: aws/build@v1 Inputs: Sources: - WorkflowSource Environment: Connections: - Role: Main-Branch-Infrastructure Name: "XXXXXXXXXXXX" Name: TerraformBootstrap Configuration: Steps: - Run: export TF_VERSION=1.5.2 && wget -O terraform.zip "https://releases.hashicorp.com/terraform/${TF_VERSION}/terraform_${TF_VERSION}_linux_amd64.zip" - Run: unzip terraform.zip && rm terraform.zip && mv terraform /usr/bin/terraform && chmod +x /usr/bin/terraform - Run: terraform init -no-color - Run: terraform validate -no-color - Run: terraform plan -no-color -input=false - Run: terraform apply -auto-approve -no-color -input=false Compute: Type: EC2
-
Terraform modules and ADO
Now, there is a GitHub issue for setup-terraform that essentially demonstrates a problem that might occur if you try to reference your Git repo from Azure Pipelines (using HTTP) without appropriate permissions or workarounds. In this issue, there are two solutions:
- Terraform apply is skipped for some reason when this GitHub action is run
-
Where can I find source code that I can practice devops with?
Have you tried the official tutorial here: https://learn.hashicorp.com/tutorials/terraform/github-actions ?
-
Looking for ideas for a large (9 month) project
Think of a simple web application you could build and deploy into a cloud environment like aws or GCP. Build your cloud infrastructure with Terraform for this application. Deploy that infrastructure and the application itself using GitOps. For example this: https://learn.hashicorp.com/tutorials/terraform/github-actions
- Pipeline IaC com Terraform e GitHub Actions
-
Terraform integrated in the deploy pipeline?
Here's an example using Github Actions: https://learn.hashicorp.com/tutorials/terraform/github-actions. You can set all kinds of conditions in the pipeline config to only trigger on certain dirs or files, like (Github Action example:
-
My First Experience Learning Terraform and Amazon ECS + AWS Fargate
You may need to use the Terraform Cloud. When you use the Terraform Cloud, please use this guide. However, it's not required for now.
-
Im at a loss for how to setup a CI/CD pipeline. REALLY need some help
Since it sounds like you're using GitHub, using GitHub Actions for any CI pipelines would be easiest. You could run terraform plan in your PRs, there's a great writeup on how to do it here. Or any unit tests, docker builds, etc. Lots of great ideas at Awesome Actions.
-
Cloud Resume Challenge - Trials & Tribulations
#11-15 The Finish Line So for the last portion of the challenge, I had to implement a test against my python code to make sure that it works as it should every time I update it. I then realized I wish I had started here first since I'd need to use IaC to deploy and configure all my resources. Reading I found that I could use SAM but instead I used Terraform/Terraform Cloud since I remember that's what many people use. I tore down almost everything that I did in the AWS console and redid everything using Terraform. I had to setup the API tokens, make a variable set using my AWS credentials and followed the tutorial on how to setup github actions and then I applied it to this challenge. I also used this resource to make a simple test. After that it was just setting up repositories for both my back end and front end.
pipeline
-
14 DevOps and SRE Tools for 2024: Your Ultimate Guide to Stay Ahead
Tekton
- GitHub Actions could be so much better
-
Distributed Traces for Testing with Tekton Pipelines and Tracetest
Tekton is an open-source framework for creating efficient CI/CD systems. This empowers developers to seamlessly construct, test, and deploy applications across various cloud environments and on-premise setups.
-
Practical Tips for Refactoring Release CI using GitHub Actions
Despite other alternatives like Circle CI, Travis CI, GitLab CI or even self-hosted options using open-source projects like Tekton or Argo Workflow, the reason for choosing GitHub Actions was straightforward: GitHub Actions, in conjunction with the GitHub ecosystem, offers a user-friendly experience and access to a rich software marketplace.
-
Wolfi: A community Linux OS designed for the container and cloud-native era
[2]: https://github.com/tektoncd/pipeline/issues/5507#issuecommen...
- Nu stiu ce sa fac, orice sfat e bine venit
-
What are some good self-hosted CI/CD tools where pipeline steps run in docker containers?
Drone, or Tekton, Argo Workflows if you’re on k8s
-
Is Jenkins still the king?
If you want a step up, I would recommend trying out Tekton Pipelines. It’s a very popular ci tool, and it runs on Kubernetes. Yes, this would involve setting up a Kubernetes cluster but please don’t run for the hills! You can setup a Kubernetes cluster and install Tekton on top of it with minimal setup using minikube (see here. This would be a great joint exercise as it will give you a bit of Kubernetes understanding alongside it, and the mechanisms of Tekton are a little trickier than GitHub actions imo. It’s all much the same though.
- Is there a way to run a one-off pod that would work as a command line tool?
-
K8s powered Git push deployments
I've recently found this quote by Kelsey Hightower:
"I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."
Source: https://twitter.com/kelseyhightower/status/85193508753294540...
In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.
My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.
Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?
Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.
Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?
What are some alternatives?
setup-tflint - A GitHub action that installs Terraform linter TFLint
dagger - Application Delivery as Code that Runs Anywhere
DataAnalyticsEnvironments - Automated real time streaming ingestion using Kafka and Databricks
argo-cd - Declarative Continuous Deployment for Kubernetes
github-script - Write workflows scripting the GitHub API in JavaScript
kubevela - The Modern Application Platform.
Workflows - Reusable workflows
tekton-argocd-poc - This a PoC using Tekton (for CI) and ArgoCD (CD). It uses a local k8s cluster (K3D)
my-aws - My AWS IAC
NUKE - 🏗 The AKEless Build System for C#/.NET
terraform-up-and-running-code - Code samples for the book "Terraform: Up & Running" by Yevgeniy Brikman
skaffold - Easy and Repeatable Kubernetes Development