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.
718
+
718
719
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:
719
720
720
-
```
721
+
When applied, a secret with the given key and value will be created in the repositories.
722
+
723
+
The value of the secrets must be given in plain text, GitHub provider is in charge of encrypting it.
724
+
725
+
**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.
741
+
742
+
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
743
+
728
744
When applied, a secret with the given key and value will be created in the repositories.
729
-
The value of the secrets must be given in plain text, github provider is in charge of encrypting it.
730
-
**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
@@ -938,19 +938,40 @@ section {
938
938
default={}
939
939
description=<<-END
940
940
This map allows you to create and manage secrets for repositories in your organization.
941
+
941
942
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:
942
943
943
-
```
944
+
When applied, a secret with the given key and value will be created in the repositories.
945
+
946
+
The value of the secrets must be given in plain text, GitHub provider is in charge of encrypting it.
947
+
948
+
**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.
949
+
END
950
+
951
+
readme_example=<<-END
944
952
plaintext_secrets = {
945
-
SECRET_NAME_1 = "secret_value_1"
946
-
SECRET_NAME_2 = "secret_value_2"
947
-
...
953
+
SECRET_NAME_1 = "plaintext_secret_value_1"
954
+
SECRET_NAME_2 = "plaintext_secret_value_2"
948
955
}
949
-
```
956
+
END
957
+
}
958
+
959
+
variable"encrypted_secrets" {
960
+
type=map(string)
961
+
default={}
962
+
description=<<-END
963
+
This map allows you to create and manage encrypted secrets for repositories in your organization.
964
+
965
+
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
950
966
951
967
When applied, a secret with the given key and value will be created in the repositories.
952
-
The value of the secrets must be given in plain text, github provider is in charge of encrypting it.
953
-
**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.
968
+
END
969
+
970
+
readme_example=<<-END
971
+
encrypted_secrets = {
972
+
SECRET_NAME_1 = "c2VjcmV0X3ZhbHVlXzE="
973
+
SECRET_NAME_2 = "c2VjcmV0X3ZhbHVlXzI="
974
+
}
954
975
END
955
976
}
956
977
@@ -998,7 +1019,7 @@ section {
998
1019
title="Module Configuration"
999
1020
1000
1021
variable"module_depends_on" {
1001
-
type=list(any)
1022
+
type=list(dependency)
1002
1023
default=[]
1003
1024
description=<<-END
1004
1025
Due to the fact, that terraform does not offer `depends_on` on modules as of today (v0.12.24)
0 commit comments