From 9785a1136202b6fce9a597a2ffd303c959255959 Mon Sep 17 00:00:00 2001 From: Hossein Abbasi <16090309+hsnabszhdn@users.noreply.github.com> Date: Thu, 3 Jul 2025 13:31:52 +1000 Subject: [PATCH] Fix 'GitLab' brand name --- .../terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx | 2 +- .../docs/cloud-docs/vcs/troubleshooting.mdx | 2 +- .../v202206-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202207-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202207-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202208-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202208-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202208-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202208-3/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202208-3/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202209-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202209-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202209-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202210-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202210-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202211-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202211-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202212-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202212-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202212-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202212-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202301-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202301-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202301-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202301-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202302-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202302-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202303-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202303-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202304-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202304-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202305-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202305-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202305-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202305-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202306-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202306-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202307-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202307-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202308-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202308-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202309-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202309-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202310-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202310-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202311-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202311-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202312-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202312-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202401-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202401-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202401-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202401-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202402-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202402-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202402-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202402-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202404-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202404-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202404-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202404-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202405-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202405-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202406-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202406-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202407-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202407-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202408-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202408-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202409-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202409-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202409-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202409-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202409-3/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202409-3/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202410-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202410-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202411-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202411-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202411-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202411-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202501-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202501-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202502-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202502-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202502-2/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202502-2/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202503-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202503-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202504-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202504-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202505-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202505-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../v202506-1/docs/enterprise/vcs/gitlab-eece.mdx | 2 +- .../v202506-1/docs/enterprise/vcs/troubleshooting.mdx | 2 +- .../admin/license-example-usage-payload.mdx | 4 ++-- content/terraform/v1.10.x/docs/language/style.mdx | 2 +- content/terraform/v1.11.x/docs/language/style.mdx | 2 +- content/terraform/v1.12.x/docs/language/style.mdx | 2 +- content/terraform/v1.2.x/docs/language/style.mdx | 2 +- content/terraform/v1.3.x/docs/language/style.mdx | 2 +- content/terraform/v1.4.x/docs/language/style.mdx | 2 +- content/terraform/v1.6.x/docs/language/style.mdx | 2 +- content/terraform/v1.7.x/docs/language/style.mdx | 2 +- content/terraform/v1.8.x/docs/language/style.mdx | 2 +- content/terraform/v1.9.x/docs/language/style.mdx | 2 +- 106 files changed, 107 insertions(+), 107 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx b/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx index 58dc5b942..48ec8a696 100644 --- a/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/vcs/gitlab-eece.mdx @@ -77,7 +77,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 1. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx b/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx index faae6ade0..18d9f5d48 100644 --- a/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/vcs/troubleshooting.mdx @@ -150,7 +150,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 ``` -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: ``` bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 diff --git a/content/terraform-enterprise/v202206-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202206-1/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202206-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202206-1/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202207-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202207-1/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202207-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202207-1/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202207-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202207-2/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202207-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202207-2/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202208-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202208-1/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202208-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202208-1/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/gitlab-eece.mdx index a8342ad06..508c61dc2 100644 --- a/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -86,7 +86,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | --> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. +-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202208-2/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/gitlab-eece.mdx index a8342ad06..508c61dc2 100644 --- a/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/gitlab-eece.mdx @@ -86,7 +86,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | --> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. +-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/troubleshooting.mdx index 8f6e40c28..c50a7acf2 100644 --- a/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202208-3/docs/enterprise/vcs/troubleshooting.mdx @@ -113,7 +113,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202209-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202209-1/docs/enterprise/vcs/troubleshooting.mdx index 9767359ee..dcf0d74e2 100644 --- a/content/terraform-enterprise/v202209-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202209-1/docs/enterprise/vcs/troubleshooting.mdx @@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/gitlab-eece.mdx index 2c0e40530..24a45db90 100644 --- a/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -87,7 +87,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | --> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. +-> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/troubleshooting.mdx index 9767359ee..dcf0d74e2 100644 --- a/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202209-2/docs/enterprise/vcs/troubleshooting.mdx @@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/troubleshooting.mdx index 9767359ee..dcf0d74e2 100644 --- a/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202210-1/docs/enterprise/vcs/troubleshooting.mdx @@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/troubleshooting.mdx index 9767359ee..dcf0d74e2 100644 --- a/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202211-1/docs/enterprise/vcs/troubleshooting.mdx @@ -114,7 +114,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/troubleshooting.mdx index 9438303c7..9ed21d819 100644 --- a/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202212-1/docs/enterprise/vcs/troubleshooting.mdx @@ -124,7 +124,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/troubleshooting.mdx index 9438303c7..9ed21d819 100644 --- a/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202212-2/docs/enterprise/vcs/troubleshooting.mdx @@ -124,7 +124,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/troubleshooting.mdx index 19259806a..8a3f6bd47 100644 --- a/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202301-1/docs/enterprise/vcs/troubleshooting.mdx @@ -126,7 +126,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/troubleshooting.mdx index 19259806a..8a3f6bd47 100644 --- a/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202301-2/docs/enterprise/vcs/troubleshooting.mdx @@ -126,7 +126,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/gitlab-eece.mdx index 693f268b9..37fc58912 100644 --- a/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -78,7 +78,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/troubleshooting.mdx index c5e7d44f6..61169c18e 100644 --- a/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202302-1/docs/enterprise/vcs/troubleshooting.mdx @@ -128,7 +128,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202303-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202304-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202305-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202305-2/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202306-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202307-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202308-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202309-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202310-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/troubleshooting.mdx index 5cd168cb2..e3647e799 100644 --- a/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202311-1/docs/enterprise/vcs/troubleshooting.mdx @@ -129,7 +129,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/troubleshooting.mdx index d0b236242..6d1410ac6 100644 --- a/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202312-1/docs/enterprise/vcs/troubleshooting.mdx @@ -142,7 +142,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/troubleshooting.mdx index d0b236242..6d1410ac6 100644 --- a/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202401-1/docs/enterprise/vcs/troubleshooting.mdx @@ -142,7 +142,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/troubleshooting.mdx index d0b236242..6d1410ac6 100644 --- a/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202401-2/docs/enterprise/vcs/troubleshooting.mdx @@ -142,7 +142,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/gitlab-eece.mdx index 8f2a674a3..3c02ec5ec 100644 --- a/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -81,7 +81,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and Terraform Cloud now refreshes tokens more often. + -> **Note:** For previous versions of Terraform Cloud and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but Terraform Cloud only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and Terraform Cloud now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/troubleshooting.mdx index d0b236242..6d1410ac6 100644 --- a/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202402-1/docs/enterprise/vcs/troubleshooting.mdx @@ -142,7 +142,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/gitlab-eece.mdx index 107f41f49..80135e669 100644 --- a/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/troubleshooting.mdx index fae935c03..7b1f8ea2e 100644 --- a/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202402-2/docs/enterprise/vcs/troubleshooting.mdx @@ -142,7 +142,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/gitlab-eece.mdx index 18b2d161e..b123b8a20 100644 --- a/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/troubleshooting.mdx index 090714d02..ebdbffe9e 100644 --- a/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202404-1/docs/enterprise/vcs/troubleshooting.mdx @@ -145,7 +145,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202404-2/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/gitlab-eece.mdx index 18b2d161e..b123b8a20 100644 --- a/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/troubleshooting.mdx index 090714d02..ebdbffe9e 100644 --- a/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202405-1/docs/enterprise/vcs/troubleshooting.mdx @@ -145,7 +145,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202406-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202407-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202408-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202409-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202409-2/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202409-3/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202410-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202411-1/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/gitlab-eece.mdx index c3c8cd28d..cc815947f 100644 --- a/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -79,7 +79,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/troubleshooting.mdx index e83a3e152..63e3da42a 100644 --- a/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202411-2/docs/enterprise/vcs/troubleshooting.mdx @@ -146,7 +146,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..2a97ea422 100644 --- a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..2a97ea422 100644 --- a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..2a97ea422 100644 --- a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..2a97ea422 100644 --- a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..1830f1488 100644 --- a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..1830f1488 100644 --- a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..1830f1488 100644 --- a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -80,7 +80,7 @@ Leave the page open in a browser tab. In the next step you will copy values from | Expire access tokens (checkbox) | (no longer required) | | Scopes (all checkboxes) | api | - -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because Gitlab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on Gitlab v15+ and HCP Terraform now refreshes tokens more often. + -> **Note:** For previous versions of HCP Terraform and GitLab, we recommended disabling a setting called `Expire access tokens`. This action was required because GitLab marked OAuth tokens as expired after 2 hours, but HCP Terraform only refreshed tokens after 6 hours. This setting does not exist on GitLab v15+ and HCP Terraform now refreshes tokens more often. 4. Click the "Save application" button, which creates the application and takes you to its page. diff --git a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..3937ee1c2 100644 --- a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx @@ -148,7 +148,7 @@ Then run the `openssl s_client` command, using the certificate at `/tmp/cust-ca- openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect git-server-hostname:443 -For example, a Gitlab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: +For example, a GitLab server that uses a self-signed certificate might result in an error like `verify error:num=18:self signed certificate`, as shown in the output below: bash-4.3# openssl s_client -showcerts -CAfile /tmp/cust-ca-certificates.crt -connect gitlab.local:443 CONNECTED(00000003) diff --git a/content/terraform-enterprise/v202506-1/docs/partials/replicated-and-fdo/admin/license-example-usage-payload.mdx b/content/terraform-enterprise/v202506-1/docs/partials/replicated-and-fdo/admin/license-example-usage-payload.mdx index 1d6645d4b..4604b7a6f 100644 --- a/content/terraform-enterprise/v202506-1/docs/partials/replicated-and-fdo/admin/license-example-usage-payload.mdx +++ b/content/terraform-enterprise/v202506-1/docs/partials/replicated-and-fdo/admin/license-example-usage-payload.mdx @@ -126,7 +126,7 @@ The following JSON payload describes the product usage data that Terraform Enter "value": 0, "mode": "write" }, - "gitlab_vcs_present": { # 1 if Gitlab is configured as a VCS provider, 0 otherwise + "gitlab_vcs_present": { # 1 if GitLab is configured as a VCS provider, 0 otherwise "key": "gitlab_vcs_present", "value": 0, "mode": "write" @@ -246,7 +246,7 @@ The following JSON payload describes the product usage data that Terraform Enter "value": 0, "mode": "write" }, - "workspace_count_gitlab": { # Workspace count connected to Gitlab + "workspace_count_gitlab": { # Workspace count connected to GitLab "key": "workspace_count_gitlab", "value": 0, "mode": "write" diff --git a/content/terraform/v1.10.x/docs/language/style.mdx b/content/terraform/v1.10.x/docs/language/style.mdx index 9bd0e3ef8..8d012a899 100644 --- a/content/terraform/v1.10.x/docs/language/style.mdx +++ b/content/terraform/v1.10.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.11.x/docs/language/style.mdx b/content/terraform/v1.11.x/docs/language/style.mdx index 9bd0e3ef8..8d012a899 100644 --- a/content/terraform/v1.11.x/docs/language/style.mdx +++ b/content/terraform/v1.11.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.12.x/docs/language/style.mdx b/content/terraform/v1.12.x/docs/language/style.mdx index 0b6e2a7b5..42d9fe95b 100644 --- a/content/terraform/v1.12.x/docs/language/style.mdx +++ b/content/terraform/v1.12.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.2.x/docs/language/style.mdx b/content/terraform/v1.2.x/docs/language/style.mdx index d43069d80..5bf3cf884 100644 --- a/content/terraform/v1.2.x/docs/language/style.mdx +++ b/content/terraform/v1.2.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.3.x/docs/language/style.mdx b/content/terraform/v1.3.x/docs/language/style.mdx index d43069d80..5bf3cf884 100644 --- a/content/terraform/v1.3.x/docs/language/style.mdx +++ b/content/terraform/v1.3.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.4.x/docs/language/style.mdx b/content/terraform/v1.4.x/docs/language/style.mdx index d43069d80..5bf3cf884 100644 --- a/content/terraform/v1.4.x/docs/language/style.mdx +++ b/content/terraform/v1.4.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.6.x/docs/language/style.mdx b/content/terraform/v1.6.x/docs/language/style.mdx index d43069d80..5bf3cf884 100644 --- a/content/terraform/v1.6.x/docs/language/style.mdx +++ b/content/terraform/v1.6.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.7.x/docs/language/style.mdx b/content/terraform/v1.7.x/docs/language/style.mdx index d43069d80..5bf3cf884 100644 --- a/content/terraform/v1.7.x/docs/language/style.mdx +++ b/content/terraform/v1.7.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.8.x/docs/language/style.mdx b/content/terraform/v1.8.x/docs/language/style.mdx index 0b9472c0d..4cca2afd1 100644 --- a/content/terraform/v1.8.x/docs/language/style.mdx +++ b/content/terraform/v1.8.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing diff --git a/content/terraform/v1.9.x/docs/language/style.mdx b/content/terraform/v1.9.x/docs/language/style.mdx index 9bd0e3ef8..8d012a899 100644 --- a/content/terraform/v1.9.x/docs/language/style.mdx +++ b/content/terraform/v1.9.x/docs/language/style.mdx @@ -652,7 +652,7 @@ If you use Terraform Community Edition, we recommend the following: If you use a custom CI/CD pipeline, review your CI/CD tool's best practices for managing sensitive values. Most tools let you access sensitive values as environment variables. For more information, refer to your CI/CD documentation. - [Using secrets in GitHub Actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) -- [Gitlab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) +- [GitLab pipeline security](https://docs.gitlab.com/ee/ci/pipelines/pipeline_security.html) - [Integrate Vault into your CI/CD pipeline](/well-architected-framework/security/security-cicd-vault) ## Integration and unit testing