forked from hashicorp/terraform-helm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
values.yaml
51 lines (43 loc) · 1.98 KB
/
values.yaml
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
# Available parameters and their default values for the Terraform chart.
# global holds values that affect multiple components of the chart.
global:
# enabled is the master enabled/disabled setting.
# If true, all Terraform Kubernetes integrations will be enabled.
# If false, no components will be installed by default and per-component
# opt-in is required, such as by setting `syncWorkspace.enabled` to true.
enabled: true
# imageK8S is the name (and tag) of the terraform-k8s Docker image that
# is used for functionality such as workspace sync. This can be overridden
# per component.
imageK8S: "hashicorp/terraform-k8s:0.1.2-alpha"
# syncWorkspace will run the workspace sync process to sync K8S Workspaces with
# Terraform Cloud workspaces.
#
# This process will deploy a Workspace Custom Resource Definition and
# Terraform Cloud Workspace Operator to the Kubernetes cluster. It requires
# a Kubernetes secret for Terraform Cloud access and sensitive variables.
syncWorkspace:
# True if you want to enable the workspace sync. Set to "-" to inherit from
# global.enabled.
enabled: "-"
image: null
# k8WatchNamespace is the Kubernetes namespace to watch for workspace
# changes and sync to Terraform Cloud. If this is not set then it will default
# to the release namespace
k8WatchNamespace: null
# Log verbosity level. One of "trace", "debug", "info", "warn", or "error".
# Defaults to "info".
logLevel: null
# Name and key of Kubernetes secret containing the Terraform CLI Configuration
# Must have Terraform Cloud Team API Token
terraformRC:
secretName: terraformrc
secretKey: credentials
# Name of Kubernetes secret containing keys and values of sensitive variables
sensitiveVariables:
secretName: workspacesecrets
# Control whether a test Pod manifest is generated when running helm template.
# When using helm install, the test Pod is not submitted to the cluster so this
# is only useful when running helm template.
tests:
enabled: true