You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This map allows you to create and manage secrets for repositories in your organization.
812
+
812
813
Each element in the map is considered a secret to be managed, being the key map the secret name and the value the corresponding secret in plain text:
813
814
814
-
```
815
+
When applied, a secret with the given key and value will be created in the repositories.
816
+
817
+
The value of the secrets must be given in plain text, GitHub provider is in charge of encrypting it.
818
+
819
+
**Attention:** You should treat state as sensitive always. It is also advised that you do not store plaintext values in your code but rather populate the encrypted_value using fields from a resource, data source or variable as, while encrypted in state, these will be easily accessible in your code. See below for an example of this abstraction.
This map allows you to create and manage encrypted secrets for repositories in your organization.
835
+
836
+
Each element in the map is considered a secret to be managed, being the key map the secret name and the value the corresponding encrypted value of the secret using the Github public key in Base64 format.b
837
+
822
838
When applied, a secret with the given key and value will be created in the repositories.
823
-
The value of the secrets must be given in plain text, github provider is in charge of encrypting it.
824
-
**Attention:** You might want to get secrets via a data source from a secure vault and not add them in plain text to your source files; so you do not commit plaintext secrets into the git repository managing your github account.
Copy file name to clipboardExpand all lines: README.tfdoc.hcl
+29-8Lines changed: 29 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1055,19 +1055,40 @@ section {
1055
1055
default={}
1056
1056
description=<<-END
1057
1057
This map allows you to create and manage secrets for repositories in your organization.
1058
+
1058
1059
Each element in the map is considered a secret to be managed, being the key map the secret name and the value the corresponding secret in plain text:
1059
1060
1060
-
```
1061
+
When applied, a secret with the given key and value will be created in the repositories.
1062
+
1063
+
The value of the secrets must be given in plain text, GitHub provider is in charge of encrypting it.
1064
+
1065
+
**Attention:** You should treat state as sensitive always. It is also advised that you do not store plaintext values in your code but rather populate the encrypted_value using fields from a resource, data source or variable as, while encrypted in state, these will be easily accessible in your code. See below for an example of this abstraction.
1066
+
END
1067
+
1068
+
readme_example=<<-END
1061
1069
plaintext_secrets = {
1062
-
SECRET_NAME_1 = "secret_value_1"
1063
-
SECRET_NAME_2 = "secret_value_2"
1064
-
...
1070
+
SECRET_NAME_1 = "plaintext_secret_value_1"
1071
+
SECRET_NAME_2 = "plaintext_secret_value_2"
1065
1072
}
1066
-
```
1073
+
END
1074
+
}
1075
+
1076
+
variable"encrypted_secrets" {
1077
+
type=map(string)
1078
+
default={}
1079
+
description=<<-END
1080
+
This map allows you to create and manage encrypted secrets for repositories in your organization.
1081
+
1082
+
Each element in the map is considered a secret to be managed, being the key map the secret name and the value the corresponding encrypted value of the secret using the Github public key in Base64 format.b
1067
1083
1068
1084
When applied, a secret with the given key and value will be created in the repositories.
1069
-
The value of the secrets must be given in plain text, github provider is in charge of encrypting it.
1070
-
**Attention:** You might want to get secrets via a data source from a secure vault and not add them in plain text to your source files; so you do not commit plaintext secrets into the git repository managing your github account.
1085
+
END
1086
+
1087
+
readme_example=<<-END
1088
+
encrypted_secrets = {
1089
+
SECRET_NAME_1 = "c2VjcmV0X3ZhbHVlXzE="
1090
+
SECRET_NAME_2 = "c2VjcmV0X3ZhbHVlXzI="
1091
+
}
1071
1092
END
1072
1093
}
1073
1094
@@ -1115,7 +1136,7 @@ section {
1115
1136
title="Module Configuration"
1116
1137
1117
1138
variable"module_depends_on" {
1118
-
type=list(any)
1139
+
type=list(dependency)
1119
1140
default=[]
1120
1141
description=<<-END
1121
1142
Due to the fact, that terraform does not offer `depends_on` on modules as of today (v0.12.24)
0 commit comments