-
Notifications
You must be signed in to change notification settings - Fork 5
120 lines (109 loc) · 5.27 KB
/
deploy-hub.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
# This workflow installs the latest version of Terraform CLI and configures the Terraform CLI configuration file
# with an API token for Terraform Cloud (app.terraform.io). On pull request events, this workflow will run
# `terraform init`, `terraform fmt`, and `terraform plan` (speculative plan via Terraform Cloud). On push events
# to the master branch, `terraform apply` will be executed.
#
# Documentation for `hashicorp/setup-terraform` is located here: https://github.com/hashicorp/setup-terraform
#
# To use this workflow, you will need to complete the following setup steps.
#
# 1. Create a `main.tf` file in the root of this repository with the `remote` backend and one or more resources defined.
# Example `main.tf`:
# # The configuration for the `remote` backend.
# terraform {
# backend "remote" {
# # The name of your Terraform Cloud organization.
# organization = "example-organization"
#
# # The name of the Terraform Cloud workspace to store Terraform state files in.
# workspaces {
# name = "example-workspace"
# }
# }
# }
#
# # An example resource that does nothing.
# resource "null_resource" "example" {
# triggers = {
# value = "A example resource that does nothing!"
# }
# }
#
#
# 2. Generate a Terraform Cloud user API token and store it as a GitHub secret (e.g. TF_API_TOKEN) on this repository.
# Documentation:
# - https://www.terraform.io/docs/cloud/users-teams-organizations/api-tokens.html
# - https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
#
# 3. Reference the GitHub secret in step using the `hashicorp/setup-terraform` GitHub Action.
# Example:
# - name: Setup Terraform
# uses: hashicorp/setup-terraform@v1
# with:
# cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
name: 'Deploy Hub VNET'
on:
push:
branches:
- master
paths:
- 'deploy-hub.txt'
pull_request:
workflow_dispatch:
# name: Workflow2
# on:
# workflow_run:
# workflows: ["Workflow1"]
# branches: [master]
# types:
# - completed
# jobs:
# job1:
# if: ${{ github.event.workflow_run.conclusion == 'success' }}
jobs:
terraform:
name: 'Create Hub VNET'
runs-on: ubuntu-latest
# Use the Bash shell regardless whether the GitHub Actions runner is ubuntu-latest, macos-latest, or windows-latest
defaults:
run:
shell: bash
working-directory: ./Terraform/Networking/Deployments/Network-Deployment/Hub-Deploy
# Checkout the repository to the GitHub Actions runner
steps:
- name: Checkout
uses: actions/checkout@v2
# Install the latest version of Terraform CLI and configure the Terraform CLI configuration file with a Terraform Cloud user API token
- name: Setup Terraform
uses: hashicorp/setup-terraform@v1
with:
# terraform_version: 0.12.25 You can use this to set the specific version of Terraform to target.
cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
# Initialize a new or existing Terraform working directory by creating initial files, loading any remote state, downloading modules, etc.
- name: Terraform Init
run: terraform init -backend-config="resource_group_name=$sa-resource_group" -backend-config="storage_account_name=$storage_account" -backend-config="container_name=$blob_storage" -backend-config="access_key=${{ secrets.SAS_KEY }}" -backend-config="key=$state_file"
env:
subscription_id: "c28db86b-8ce1-4755-aa09-fc99f6e0a667"
application_id: "12c58cc6-53c7-4a2f-bcbc-05ab4e794ebd"
tenant_id: "b033afe0-c9e4-48f6-99d3-d00269efb830"
sa-resource_group: "GH-IaC-Using-Terraform"
storage_account: "ghiacusingterraform"
blob_storage: "tfstate"
state_file: "tf-statefile-hub.state"
# Checks that all Terraform configuration files adhere to a canonical format
# - name: Terraform Format
# run: terraform fmt -check
# Generates an execution plan for Terraform
- name: Terraform Plan
run: terraform plan -var="client_id=$application_id" -var="client_secret=${{ secrets.spn_azuredevops_password }}" -var="tenant_id=$tenant_id" -var="subscription_id=$subscription_id" -var-file="Hub.tfvars" -out="HubDeploy.plan"
# Error: Saving a generated plan is currently not supported. (So, no -out *.plan file :-( )
# Error: Run variables are currently not supported. (So, no -var-file='*.tfvars' file :-(, must use *.auto.tfvars instead)
env:
subscription_id: "c28db86b-8ce1-4755-aa09-fc99f6e0a667"
application_id: "12c58cc6-53c7-4a2f-bcbc-05ab4e794ebd"
tenant_id: "b033afe0-c9e4-48f6-99d3-d00269efb830"
# On push to master, build or change infrastructure according to Terraform configuration files
# Note: It is recommended to set up a required "strict" status check in your repository for "Terraform Cloud". See the documentation on "strict" required status checks for more information: https://help.github.com/en/github/administering-a-repository/types-of-required-status-checks
- name: Terraform Apply
if: github.ref == 'refs/heads/master' && github.event_name == 'push' || github.event_name == 'workflow_dispatch'
run: terraform apply HubDeploy.plan