GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
fix: remove unnecessary nesting of secret data for KV-V1 secrets: (#1570)
NOTES:
vault_kv_secret no longer stores secrets in Vault under a nested data object.
In versions 3.8.1 and below, the kv resource inadvertently nested the value under data.
To remedy this please update any consumers of this KV and run a terraform apply to properly set the value.
Configuration
Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
Automerge: Disabled by config. Please merge this manually once you are satisfied.
Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.
Ignore: Close this MR and you won't be reminded about this update again.
If you want to rebase/retry this MR, click this checkbox.
