{"id":97895,"date":"2020-10-23T02:42:12","date_gmt":"2020-10-23T00:42:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd"},"modified":"2020-10-23T02:42:12","modified_gmt":"2020-10-23T00:42:12","slug":"kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/kak-ispolzovat-hashicorp-waypoint-dlya-sovmestnoj-raboty-s-gitlab-ci-cd","title":{"rendered":"How to Use HashiCorp Waypoint for Collaboration with GitLab CI\/CD","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"How<\/p>\n

<\/p>\n

HashiCorp has introduced a new project Waypoint<\/a><\/noindex> to HashiCorp Digital<\/a><\/noindex>. It uses an HCL-based file to describe the build, delivery, and release of applications across various cloud platforms, from Kubernetes to AWS and Google Cloud Run. One could think of Waypoint as a combination of Terraform and Vagrant for outlining the process of building, delivering, and releasing your applications.<\/p>\n

<\/a><\/noindex><\/p>\n

Staying true to itself, HashiCorp released Waypoint as open-source, complete with numerous examples. The level of orchestration is up to you; Waypoint comes as an executable that you can run directly on your laptop or from your chosen CI\/CD orchestration tool. The target for application deployment is also your choice, as Waypoint supports Kubernetes, Docker, Google Cloud Run, AWS ECS, and more.<\/p>\n

<\/p>\n

After reading the stunning documentation<\/a><\/noindex> and magnificent examples<\/a><\/noindex> of applications provided by HashiCorp, we decided to take a closer look at orchestrating Waypoint with GitLab CI\/CD. To do this, we will take a simple Node.js application running on AWS ECS from the example repository.<\/p>\n

<\/p>\n

After cloning the repository, let's look at the structure of the application that displays a single page:<\/p>\n

<\/p>\n

\"How<\/p>\n

<\/p>\n

As you might have noticed, there is no Dockerfile in this project. They haven't been added in the example because they aren't needed at all, since Waypoint will take care of them for us. Let's take a closer look at the file waypoint.hcl<\/code>, to understand what it will do:<\/p>\n

<\/p>\n

project = \"example-nodejs\"\n\napp \"example-nodejs\" {\n  labels = {\n    \"service\" = \"example-nodejs\",\n    \"env\" = \"dev\"\n  }\n\n  build {\n    use \"pack\" {}\n    registry {\n    use \"aws-ecr\" {\n        region = \"us-east-1\"\n        repository = \"waypoint-gitlab\"\n        tag = \"latest\"\n    }\n    }\n  }\n\n  deploy {\n    use \"aws-ecs\" {\n    region = \"us-east-1\"\n    memory = \"512\"\n    }\n  }\n}<\/code><\/pre>\n
<\/p>\n
During the build stage, Waypoint uses Cloud Native Buildpacks (CNB<\/a><\/noindex>), to determine the programming language of the project and create a Docker image without using a Dockerfile. Essentially, this is the same technology used by GitLab in the Auto DevOps<\/a><\/noindex> Auto Build step. It's nice to see that CNB from CNCF is gaining more traction among industry users.<\/p>\n
<\/p>\n
Once the image is built, Waypoint will automatically push it to our AWS ECR registry, ready for delivery. After the build is complete, the delivery step uses the AWS ECS plugin<\/a><\/noindex> to deploy our application to our AWS account.<\/p>\n
<\/p>\n
From my laptop \u2014 it's all straightforward. I set up Waypoint, which is already authenticated with my AWS account, and it 'just works.' But what if I want to go beyond my laptop? Or suddenly I want to automate this deployment as part of my overall CI\/CD pipeline, where my current integration tests, security tests, and others run? This is where GitLab CI\/CD comes into the story!<\/p>\n
<\/p>\n
N.B.<\/strong> If you're just planning to implement CI\/CD or want to start applying best practices in building pipelines, check out the new course from Slyer. \u201cCI\/CD using GitLab CI\u201d<\/a><\/noindex>. It is currently available at a pre-order price. <\/p><\/blockquote>\n
<\/p>\n
Waypoint in GitLab CI\/CD<\/h2>\n
<\/p>\n
To orchestrate all this in GitLab CI\/CD, let's see what we need in our file. .gitlab-ci.yml<\/code>:<\/p>\n
<\/p>\n