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
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -477,6 +477,7 @@ statement instead the previous block.
477
477
| <aname="input_create_cd_toolchain"></a> [create\_cd\_toolchain](#input\_create\_cd\_toolchain)| Boolean flag which determines if the DevSecOps CD toolchain is created. |`bool`|`true`| no |
478
478
| <aname="input_create_ci_toolchain"></a> [create\_ci\_toolchain](#input\_create\_ci\_toolchain)| Flag which determines if the DevSecOps CI toolchain is created. If this toolchain is not created then values must be set for the following variables, evidence\_repo\_url, issues\_repo\_url and inventory\_repo\_url. |`bool`|`true`| no |
479
479
| <aname="input_create_cos_api_key"></a> [create\_cos\_api\_key](#input\_create\_cos\_api\_key)| Set to `true` to create and add a `cos-api-key` to the Secrets Provider. |`bool`|`false`| no |
480
+
| <aname="input_create_git_token"></a> [create\_git\_token](#input\_create\_git\_token)| Set to `true` to create and add the specified personal access token secret to the Secrets Provider. |`bool`|`false`| no |
480
481
| <aname="input_create_ibmcloud_api_key"></a> [create\_ibmcloud\_api\_key](#input\_create\_ibmcloud\_api\_key)| Set to `true` to create and add an `ibmcloud-api-key` to the Secrets Provider. |`bool`|`false`| no |
481
482
| <aname="input_create_icr_namespace"></a> [create\_icr\_namespace](#input\_create\_icr\_namespace)| Set to `true` to have Terraform create the registry namespace. Setting to `false` will have the CI pipeline create the namespace if it does not already exist. Note: If a Terraform destroy is used, the ICR namespace along with all images will be removed. |`bool`|`false`| no |
482
483
| <aname="input_create_secret_group"></a> [create\_secret\_group](#input\_create\_secret\_group)| Set to `true` to create the specified Secrets Manager secret group. |`bool`|`false`| no |
@@ -545,6 +546,7 @@ statement instead the previous block.
545
546
| <aname="input_registry_namespace"></a> [registry\_namespace](#input\_registry\_namespace)| A unique namespace within the IBM Cloud Container Registry region where the application image is stored. |`string`|`""`| no |
546
547
| <aname="input_repo_git_token_secret_crn"></a> [repo\_git\_token\_secret\_crn](#input\_repo\_git\_token\_secret\_crn)| The CRN for the repositories Git Token. |`string`|`""`| no |
547
548
| <aname="input_repo_git_token_secret_name"></a> [repo\_git\_token\_secret\_name](#input\_repo\_git\_token\_secret\_name)| Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`. |`string`|`""`| no |
549
+
| <aname="input_repo_git_token_secret_value"></a> [repo\_git\_token\_secret\_value](#input\_repo\_git\_token\_secret\_value)| The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider. |`string`|`""`| no |
548
550
| <aname="input_repo_group"></a> [repo\_group](#input\_repo\_group)| Specify the Git user or group for your application. This must be set if the repository authentication type is `pat` (personal access token). |`string`|`""`| no |
549
551
| <aname="input_repo_secret_group"></a> [repo\_secret\_group](#input\_repo\_secret\_group)| Secret group in Secrets Manager that contains the secret for the repository. This variable will set the same secret group for all the repositories. Can be overriden on a per secret group basis. Only applies when using Secrets Manager. |`string`|`""`| no |
550
552
| <aname="input_repositories_prefix"></a> [repositories\_prefix](#input\_repositories\_prefix)| Prefix name for the cloned compliance repos. For the repositories\_prefix value only a-z, A-Z and 0-9 and the special characters `-_` are allowed. In addition the string must not end with a special character or have two consecutive special characters. |`string`|`"compliance"`| no |
Copy file name to clipboardExpand all lines: ibm_catalog.json
+28Lines changed: 28 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1066,6 +1066,13 @@
1066
1066
"description": "Set to `true` to create and add a `cos-api-key` to the Secrets Provider.",
1067
1067
"required": false
1068
1068
},
1069
+
{
1070
+
"key": "create_git_token",
1071
+
"type": "boolean",
1072
+
"default_value": false,
1073
+
"description": "Set to `true` to create and add the specified personal access token secret to the Secrets Provider.",
1074
+
"required": false
1075
+
},
1069
1076
{
1070
1077
"key": "create_ibmcloud_api_key",
1071
1078
"type": "boolean",
@@ -1486,6 +1493,13 @@
1486
1493
"description": "Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`.",
1487
1494
"required": false
1488
1495
},
1496
+
{
1497
+
"key": "repo_git_token_secret_value",
1498
+
"type": "password",
1499
+
"default_value": "",
1500
+
"description": "The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider.",
1501
+
"required": false
1502
+
},
1489
1503
{
1490
1504
"key": "repo_group",
1491
1505
"type": "string",
@@ -2848,6 +2862,13 @@
2848
2862
"description": "Set to `true` to create and add a `cos-api-key` to the Secrets Provider.",
2849
2863
"required": false
2850
2864
},
2865
+
{
2866
+
"key": "create_git_token",
2867
+
"type": "boolean",
2868
+
"default_value": false,
2869
+
"description": "Set to `true` to create and add the specified personal access token secret to the Secrets Provider.",
2870
+
"required": false
2871
+
},
2851
2872
{
2852
2873
"key": "create_ibmcloud_api_key",
2853
2874
"type": "boolean",
@@ -3268,6 +3289,13 @@
3268
3289
"description": "Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`.",
3269
3290
"required": false
3270
3291
},
3292
+
{
3293
+
"key": "repo_git_token_secret_value",
3294
+
"type": "password",
3295
+
"default_value": "",
3296
+
"description": "The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider.",
description="Set to `true` to create and add the specified personal access token secret to the Secrets Provider."
46
+
default=false
47
+
}
48
+
49
+
variable"repo_git_token_secret_name" {
50
+
type=string
51
+
description="Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`."
52
+
default=""
53
+
}
54
+
55
+
variable"repo_git_token_secret_value" {
56
+
type=string
57
+
sensitive=true
58
+
description="The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider."
59
+
default=""
60
+
}
61
+
43
62
variable"sm_exists" {
44
63
description="Only connect to the Secrets Manager instance if it has been enabled for the toolchain."
Copy file name to clipboardExpand all lines: solutions/code-engine/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -461,6 +461,7 @@ No resources.
461
461
| <aname="input_create_cd_toolchain"></a> [create\_cd\_toolchain](#input\_create\_cd\_toolchain)| Boolean flag which determines if the DevSecOps CD toolchain is created. |`bool`|`true`| no |
462
462
| <aname="input_create_ci_toolchain"></a> [create\_ci\_toolchain](#input\_create\_ci\_toolchain)| Flag which determines if the DevSecOps CI toolchain is created. If this toolchain is not created then values must be set for the following variables, evidence\_repo\_url, issues\_repo\_url and inventory\_repo\_url. |`bool`|`true`| no |
463
463
| <aname="input_create_cos_api_key"></a> [create\_cos\_api\_key](#input\_create\_cos\_api\_key)| Set to `true` to create and add a `cos-api-key` to the Secrets Provider. |`bool`|`false`| no |
464
+
| <aname="input_create_git_token"></a> [create\_git\_token](#input\_create\_git\_token)| Set to `true` to create and add the specified personal access token secret to the Secrets Provider. |`bool`|`false`| no |
464
465
| <aname="input_create_ibmcloud_api_key"></a> [create\_ibmcloud\_api\_key](#input\_create\_ibmcloud\_api\_key)| Set to `true` to create and add an `ibmcloud-api-key` to the Secrets Provider. |`bool`|`false`| no |
465
466
| <aname="input_create_icr_namespace"></a> [create\_icr\_namespace](#input\_create\_icr\_namespace)| Set to `true` to have Terraform create the registry namespace. Setting to `false` will have the CI pipeline create the namespace if it does not already exist. Note: If a Terraform destroy is used, the ICR namespace along with all images will be removed. |`bool`|`false`| no |
466
467
| <aname="input_create_secret_group"></a> [create\_secret\_group](#input\_create\_secret\_group)| Set to `true` to create the specified Secrets Manager secret group. |`bool`|`false`| no |
@@ -529,6 +530,7 @@ No resources.
529
530
| <aname="input_registry_namespace"></a> [registry\_namespace](#input\_registry\_namespace)| A unique namespace within the IBM Cloud Container Registry region where the application image is stored. |`string`|`""`| no |
530
531
| <aname="input_repo_git_token_secret_crn"></a> [repo\_git\_token\_secret\_crn](#input\_repo\_git\_token\_secret\_crn)| The CRN for the repositories Git Token. |`string`|`""`| no |
531
532
| <aname="input_repo_git_token_secret_name"></a> [repo\_git\_token\_secret\_name](#input\_repo\_git\_token\_secret\_name)| Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`. |`string`|`""`| no |
533
+
| <aname="input_repo_git_token_secret_value"></a> [repo\_git\_token\_secret\_value](#input\_repo\_git\_token\_secret\_value)| The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider. |`string`|`""`| no |
532
534
| <aname="input_repo_group"></a> [repo\_group](#input\_repo\_group)| Specify the Git user or group for your application. This must be set if the repository authentication type is `pat` (personal access token). |`string`|`""`| no |
533
535
| <aname="input_repo_secret_group"></a> [repo\_secret\_group](#input\_repo\_secret\_group)| Secret group in Secrets Manager that contains the secret for the repository. This variable will set the same secret group for all the repositories. Can be overriden on a per secret group basis. Only applies when using Secrets Manager. |`string`|`""`| no |
534
536
| <aname="input_repositories_prefix"></a> [repositories\_prefix](#input\_repositories\_prefix)| Prefix name for the cloned compliance repos. For the repositories\_prefix value only a-z, A-Z and 0-9 and the special characters `-_` are allowed. In addition the string must not end with a special character or have two consecutive special characters. |`string`|`"compliance"`| no |
description="The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider."
691
+
default=""
692
+
}
693
+
681
694
variable"repo_group" {
682
695
type=string
683
696
description="Specify the Git user or group for your application. This must be set if the repository authentication type is `pat` (personal access token)."
Copy file name to clipboardExpand all lines: solutions/kubernetes/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -461,6 +461,7 @@ No resources.
461
461
| <aname="input_create_cd_toolchain"></a> [create\_cd\_toolchain](#input\_create\_cd\_toolchain)| Boolean flag which determines if the DevSecOps CD toolchain is created. |`bool`|`true`| no |
462
462
| <aname="input_create_ci_toolchain"></a> [create\_ci\_toolchain](#input\_create\_ci\_toolchain)| Flag which determines if the DevSecOps CI toolchain is created. If this toolchain is not created then values must be set for the following variables, evidence\_repo\_url, issues\_repo\_url and inventory\_repo\_url. |`bool`|`true`| no |
463
463
| <aname="input_create_cos_api_key"></a> [create\_cos\_api\_key](#input\_create\_cos\_api\_key)| Set to `true` to create and add a `cos-api-key` to the Secrets Provider. |`bool`|`false`| no |
464
+
| <aname="input_create_git_token"></a> [create\_git\_token](#input\_create\_git\_token)| Set to `true` to create and add the specified personal access token secret to the Secrets Provider. |`bool`|`false`| no |
464
465
| <aname="input_create_ibmcloud_api_key"></a> [create\_ibmcloud\_api\_key](#input\_create\_ibmcloud\_api\_key)| Set to `true` to create and add an `ibmcloud-api-key` to the Secrets Provider. |`bool`|`false`| no |
465
466
| <aname="input_create_icr_namespace"></a> [create\_icr\_namespace](#input\_create\_icr\_namespace)| Set to `true` to have Terraform create the registry namespace. Setting to `false` will have the CI pipeline create the namespace if it does not already exist. Note: If a Terraform destroy is used, the ICR namespace along with all images will be removed. |`bool`|`false`| no |
466
467
| <aname="input_create_secret_group"></a> [create\_secret\_group](#input\_create\_secret\_group)| Set to `true` to create the specified Secrets Manager secret group. |`bool`|`false`| no |
@@ -529,6 +530,7 @@ No resources.
529
530
| <aname="input_registry_namespace"></a> [registry\_namespace](#input\_registry\_namespace)| A unique namespace within the IBM Cloud Container Registry region where the application image is stored. |`string`|`""`| no |
530
531
| <aname="input_repo_git_token_secret_crn"></a> [repo\_git\_token\_secret\_crn](#input\_repo\_git\_token\_secret\_crn)| The CRN for the repositories Git Token. |`string`|`""`| no |
531
532
| <aname="input_repo_git_token_secret_name"></a> [repo\_git\_token\_secret\_name](#input\_repo\_git\_token\_secret\_name)| Name of the Git token secret in the secret provider. Specifying a secret name for the Git Token automatically sets the authentication type to `pat`. |`string`|`""`| no |
533
+
| <aname="input_repo_git_token_secret_value"></a> [repo\_git\_token\_secret\_value](#input\_repo\_git\_token\_secret\_value)| The personal access token that will be added to the `repo_git_token_secret_name` secret in the secrets provider. |`string`|`""`| no |
532
534
| <aname="input_repo_group"></a> [repo\_group](#input\_repo\_group)| Specify the Git user or group for your application. This must be set if the repository authentication type is `pat` (personal access token). |`string`|`""`| no |
533
535
| <aname="input_repo_secret_group"></a> [repo\_secret\_group](#input\_repo\_secret\_group)| Secret group in Secrets Manager that contains the secret for the repository. This variable will set the same secret group for all the repositories. Can be overriden on a per secret group basis. Only applies when using Secrets Manager. |`string`|`""`| no |
534
536
| <aname="input_repositories_prefix"></a> [repositories\_prefix](#input\_repositories\_prefix)| Prefix name for the cloned compliance repos. For the repositories\_prefix value only a-z, A-Z and 0-9 and the special characters `-_` are allowed. In addition the string must not end with a special character or have two consecutive special characters. |`string`|`"compliance"`| no |
0 commit comments