github-script VS setup-terraform

It's also possible to use output through the github-script action.

I wrote a custom script to parse PR comments as input commands to interface with Terraform CLI, returning the output as bot comments. Each step of the workflow relies on GitHub Actions, including actions/github-script to interact with GitHub's API (while brushing up on my JavaScript!).

You can generate what to annotate with a few lines of shell and then use gihub-script

Nice idea, worth mentioning other features:

* Reusable workflows (note: matrix strategy doesn't work here): https://docs.github.com/en/actions/using-workflows/reusing-w...

* Composite actions: https://docs.github.com/en/actions/creating-actions/creating...

* Script as action: https://github.com/actions/github-script

* Using GitHub Packages and artifacts: https://docs.github.com/en/actions/publishing-packages/about...

* Using docker-compose-like services that run alongside of the container: https://docs.github.com/en/actions/using-containerized-servi...

And many, many more :)

actions/github-script@v5

This workflow makes use of the awesome github-script that makes working with API's a breeze!

GitHub support hasn't been helpful so far. If you use Chrome on Linux, type xfce4-screenshooter or flameshot and grab a screenshot. Then navigate to any issue or PR, for example, https://github.com/actions/github-script/issues/187 and in the comment box at the bottom, type Ctrl-V. Either you'll see your image get uploaded or you won't. You don't need to save nor submit the comment.

Note at the end of the bash, and we are leveraging a curl command to talk directly to the GitHub API. This curl command is meant for simplicity. All of this could have been done using the octokit.rest.js library or better github-script.

In this post, I am going to focus on the API and actions/github-script. This action makes it easy to quickly write a script in your workflow that uses the GitHub API and includes the workflow run context.

My new github action follows a simple workflow: Whenever a user opens a pull request to the repository with the configured workflow, a comment is made on the PR with a greeting to the user and another comment with the statistics about the repository and PR are posted. Used the github-scripts (https://github.com/actions/github-script) action to get the API and context to write my own script in the workflow. It was a very fun exercise for me. Thankyou Dev Team for this cool contest!

# 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

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:

Have you tried the official tutorial here: https://learn.hashicorp.com/tutorials/terraform/github-actions ?

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

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:

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.

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.

#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.