This is a GitHub template repo, so when you click "Use this template", it will create a new copy of this template in your org or personal repo of choice. Once you have created a repo from this template, you should be able to clone and navigate to the root of the repository.
.
├── .github
│ └── workflows
│ ├── 0-azure.yml
│ ├── 0-azure-empty.yml
│ └── 0-azure-storage.yml
└── 0-azure
├── README.md
├── azuredeploy.json
└── DEPLOY.shInstructions on how to create an Azure Service Principal and create a GitHub Actions Secret (AZURE_CREDENTIALS) that will authenticate your GitHub Actions workflow to the Cloud.
This step is a requirement for 2. Serverless Go Functions and 3. Containers and Serverless Container Instances
Our first Azure Actions workflow, triggered on push and workflow_dispatch events, that will use the azure/login@v1 action to authenticate using the AZURE_CREDENTIALS GitHub secret, and run 0-azure/DEPLOY.sh which runs two Azure CLI commands, az group show and az resource list.
A manually triggered (workflow_dispatch) workflow that will use az deployment group create to deploy an empty Azure Resource Manager (ARM) template, azuredeploy.json, that will remove all the Azure Resources in our Resource Group.
A stand-alone action (currently triggered on workflow_dispatch) that will install our Go CLI for Azure Storage, azcopy, authenticate against Azure using our Service Principal from our AZURE_CREDENTIALS GitHub Secret, and use the azcopy sync command to sync the contents of our local repository to an Azure Storage Container.
Note: you will need to tweak this workflow according to how you would like to use it.
.
├── .github
│ └── workflows
│ └── 2-functions.yml
└── 2-functions
├── README.md
├── ...
├── BUILD.sh
└── DEPLOY.sh
├── main.go
├── host.json
├── healthz
│ └── function.json
└── TimerTrigger
└── function.jsonLinks to this README.md.
Similar to 0-azure.yml, this workflow runs our 2-functions/DEPLOY.sh. It is triggered on push event, which is filtered to the path 2-functions/**.
A bash script that uses the Azure CLI (az) to deploy a Serverless Go Function via Azure Functions custom handlers (preview), that brings Go support to Functions.
- Create an Azure Storage account (
az storage account create) - Create an Azure Functions App with Azure Functions custom handlers (
az functionapp create) - Set an environment variable,
SERVER_NAME, for our application (az functionapp config appsettings) that includes theGITHUB_SHAvariable in the formathello-gopher-${GITHUB_SHA}" - Build our Go binary via
BUILD.sh, using the Go version installed by default within GitHub Actions. Note: Commented out is the option to usedocker runandBUILD.shto build our binary using thegolang:1.15.3containers. zipour binary todeploy.zipand deploy it to Azure Functions (az functionapp deployment)- Confirm our function is up and running by running
curlagainst ourhttps://${FUNCTION_NAME}.azurewebsites.net/api/healthz, which outputs the name of the function, including theGITHUB_SHAabove.
Builds our Go binary as above. Optionally used inside a docker container should we choose to build our Go application inside of Docker.
The entrypoint for our Go Functions application. A simple HTTP web server.
The function definition for our /api/healthz endpoint which is triggered via an HTTP Trigger.
The function definition for our TimerTrigger function, which is triggered via a cron-style Timer trigger.
.
├── .github
│ └── workflows
│ └── 3-containers.yml
└── 3-containers
├── README.md
├── Dockerfile
├── main.go
└── DEPLOY.shLinks to this README.md
Similar to 0-azure.yml, this workflow runs our 3-containers/DEPLOY.sh. It is triggered on push event, which is filtered to the path 3-containers/**.
A bash script that uses the Azure CLI (az) to:
- Create an Azure Container Registry (
az acr create) - Build our docker container, which builds our Go HTTP application via multi-stage build, inside the registry using Azure Container Registry Tasks (
az acr build) - Get the credentials for our private Container Registry (
az acr get-credentials) - Deploy our container as an Azure Container Instance (
az container create), listening on Port 80
A simple Dockerfile that uses golang:rc-alpine image to perform a multi-stage build of our hello-echo echo server, using a scratch as the output image.
A simple Go echo-server that listens on 3 endpoints, /, /echo and /host, with the ability to override the default port (80) via the LISTEN_PORT environment variable.
The httpLog function logs incoming requests to standard error.