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
+1-1
Original file line number
Diff line number
Diff line change
@@ -478,7 +478,7 @@ Made with [contributors-img](https://contrib.rocks).
478
478
| <aname="input_enable_docker_machine_ssm_access"></a> [enable\_docker\_machine\_ssm\_access](#input\_enable\_docker\_machine\_ssm\_access)| Add IAM policies to the docker-machine instances to connect via the Session Manager. |`bool`|`false`| no |
479
479
| <aname="input_enable_eip"></a> [enable\_eip](#input\_enable\_eip)| Enable the assignment of an EIP to the gitlab runner instance |`bool`|`false`| no |
480
480
| <aname="input_enable_kms"></a> [enable\_kms](#input\_enable\_kms)| Let the module manage a KMS key, logs will be encrypted via KMS. Be-aware of the costs of an custom key. |`bool`|`false`| no |
481
-
| <aname="input_enable_manage_gitlab_token"></a> [enable\_manage\_gitlab\_token](#input\_enable\_manage\_gitlab\_token)| Boolean to enable the management of the GitLab token in SSM. If `true` the token will be stored in SSM, which means the SSM property is a terraform managed resource. If `false` the Gitlab token will be stored in the SSM by the user-data script during creation of the the instance. However the SSM parameter is not managed by terraform and will remain in SSM after a `terraform destroy`. |`bool`|`true`| no |
481
+
| <aname="input_enable_manage_gitlab_token"></a> [enable\_manage\_gitlab\_token](#input\_enable\_manage\_gitlab\_token)|(Deprecated and ignored) Boolean to enable the management of the GitLab token in SSM. If `true` the token will be stored in SSM, which means the SSM property is a terraform managed resource. If `false` the Gitlab token will be stored in the SSM by the user-data script during creation of the the instance. However the SSM parameter is not managed by terraform and will remain in SSM after a `terraform destroy`. |`bool`|`true`| no |
482
482
| <aname="input_enable_ping"></a> [enable\_ping](#input\_enable\_ping)| Allow ICMP Ping to the ec2 instances. |`bool`|`false`| no |
483
483
| <aname="input_enable_runner_ssm_access"></a> [enable\_runner\_ssm\_access](#input\_enable\_runner\_ssm\_access)| Add IAM policies to the runner agent instance to connect via the Session Manager. |`bool`|`false`| no |
484
484
| <aname="input_enable_runner_user_data_trace_log"></a> [enable\_runner\_user\_data\_trace\_log](#input\_enable\_runner\_user\_data\_trace\_log)| Enable bash xtrace for the user data script that creates the EC2 instance for the runner agent. Be aware this could log sensitive data such as you GitLab runner token. |`bool`|`true`| no |
description="Boolean to enable the management of the GitLab token in SSM. If `true` the token will be stored in SSM, which means the SSM property is a terraform managed resource. If `false` the Gitlab token will be stored in the SSM by the user-data script during creation of the the instance. However the SSM parameter is not managed by terraform and will remain in SSM after a `terraform destroy`."
612
+
description="(Deprecated) Boolean to enable the management of the GitLab token in SSM. If `true` the token will be stored in SSM, which means the SSM property is a terraform managed resource. If `false` the Gitlab token will be stored in the SSM by the user-data script during creation of the the instance. However the SSM parameter is not managed by terraform and will remain in SSM after a `terraform destroy`."
0 commit comments