Skip to content

Commit 8251294

Browse files
authored
Update variables.mdx (#1774)
1 parent 4e9132e commit 8251294

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/team/features/variables.mdx

+6-6
Original file line numberDiff line numberDiff line change
@@ -2,28 +2,28 @@
22
title: "Variables & Secrets"
33
---
44

5-
Digger supports per-project Variables that are made available as environment variables to terraform / opentofu at runtime.
5+
Digger supports per-project Variables that are made available as environment variables to Terraform / OpenTofu at runtime.
66
Variables are stored on the backend and passed to the job via the Job Spec.
77

8-
You can manage variables in the TFVars tab of every project.
8+
You can manage variables in the `TFVars` tab of every project.
99

1010
There are 2 types of variables: Plain Text and Secret.
1111

1212
# Plain Text variables
1313

14-
They are stored on the backend as-is and are not secured in any special way beyond standard transport and at-rest encryption in the infrastructure. Plain Text variable should only be used for non-sensitive data, like configuration parameters that differ across environments.
14+
They are stored on the backend as-is and are not secured in any special way beyond standard transport and at-rest encryption in the infrastructure. Plain Text variables should only be used for non-sensitive data, like configuration parameters that differ across environments.
1515

1616
# Secret variables
1717

1818
These variables are stored in the database encrypted with your organisation's Secret Key. It's an RSA public key that you can create in Organisation Settings. You will not be able to create Secret Variables until you have created your Secret Key as follows:
1919

20-
1. Go to your Organisation Settings and click Create Secrets Key
20+
1. Go to your Organisation Settings and click Create Secret Key
2121
2. Copy the private key and save it in your GitHub Actions as an org-level secret named `DIGGER_PRIVATE_KEY`
2222

2323
<Note>
2424
The key pair is generated in the front-end, and only shown once. At no point
25-
the private key is saved or accessed by Digger services. If you lose your
26-
private key, you will also lose ability to decrypt your secrets created using
25+
is the private key saved or accessed by Digger services. If you lose your
26+
private key, you will also lose the ability to decrypt your secrets created using
2727
that key - so you will need to re-create all your secrets in all projects.
2828
</Note>
2929

0 commit comments

Comments
 (0)