Commit 99ead823 authored by Pierre Smeyers's avatar Pierre Smeyers
Browse files

docs: remove mentions of CI_JOB_JWT_V2

parent f5345a3f

README.md

+0 −34
Original line number Diff line number Diff line
@@ -79,23 +79,6 @@ The GCP template supports a [federated authentication using OpenID Connect](http 


If you wish to use this authentication mode, please activate and configure the [OIDC variant](#oidc-variant). 



The template supports two ways to retrieve the JSON web token (JWT):



* using GitLab's `CI_JOB_JWT_V2` variable - _default_<br/>

  :warning: deprecated, scheduled to be removed in GitLab 16.5

* using an [ID token](https://docs.gitlab.com/ee/ci/yaml/index.html#id_tokens) named `GCP_JWT` - _configurable_



The ID token can be configured as follows in your `.gitlab-ci.yml` file:



```yaml

# enable GCP_JWT ID token for GCP jobs only

.gcp-base:

  id_tokens:

    GCP_JWT:

      # use your own audience url here

      aud: https://gitlab.com

```



### Deployment context variables



In order to manage the various deployment environments, this template provides a couple of **dynamic variables**
@@ -503,23 +486,6 @@ With: 
| `secret_path` (_path parameter_) | this is your secret location in the Vault server |

| `field` (_query parameter_)      | parameter to access a single basic field from the secret JSON payload |



The variant supports two ways to retrieve the JSON web token (JWT):



* using GitLab's `CI_JOB_JWT` variable - _default_<br/>

  :warning: deprecated, scheduled to be removed in GitLab 16.5

* using an [ID token](https://docs.gitlab.com/ee/ci/yaml/index.html#id_tokens) named `VAULT_JWT_TOKEN` - _configurable_



The ID token can be configured as follows in your `.gitlab-ci.yml` file:



```yaml

# enable VAULT_JWT_TOKEN ID token for GCP jobs only

.gcp-base:

  id_tokens:

    VAULT_JWT_TOKEN:

      # use your own audience url here

      aud: https://gitlab.com

```



#### Example



```yaml