From cf6680934924235f9c6574ad62a35f2e1ee11925 Mon Sep 17 00:00:00 2001 From: Michael Smith Date: Thu, 31 Jul 2025 20:50:37 -0400 Subject: [PATCH] fix: update HCP vault links to use current URL patterns (#275) Realized this was an issue while fixing how we're rendering GFM alerts on the Registry website. ## Description Basically, the URLs we're using right now are technically valid, but they were using the old URL pattern from before we created the `coder/registry` repo. The Registry website has logic to handle redirects for these, but we should avoid triggering it as it adds unnecessary entries to the user's browser history. ### Changes made - Updated all Registry links in the HCP Vault alert to include `coder` as the namespace ## Type of Change - [ ] New module - [ ] Bug fix - [ ] Feature/enhancement - [x] Documentation - [ ] Other ## Testing & Validation - [x] Tests pass (`bun test`) - [x] Code formatted (`bun run fmt`) - [x] Changes tested locally --- registry/coder/modules/hcp-vault-secrets/README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/registry/coder/modules/hcp-vault-secrets/README.md b/registry/coder/modules/hcp-vault-secrets/README.md index 30f0c407..52edd8ef 100644 --- a/registry/coder/modules/hcp-vault-secrets/README.md +++ b/registry/coder/modules/hcp-vault-secrets/README.md @@ -15,9 +15,9 @@ tags: [integration, vault, hashicorp, hvs] > > **Use these Coder registry modules instead:** > -> - **[vault-token](https://registry.coder.com/modules/vault-token)** - Connect to Vault using access tokens -> - **[vault-jwt](https://registry.coder.com/modules/vault-jwt)** - Connect to Vault using JWT/OIDC authentication -> - **[vault-github](https://registry.coder.com/modules/vault-github)** - Connect to Vault using GitHub authentication +> - **[vault-token](https://registry.coder.com/modules/coder/vault-token)** - Connect to Vault using access tokens +> - **[vault-jwt](https://registry.coder.com/modules/coder/vault-jwt)** - Connect to Vault using JWT/OIDC authentication +> - **[vault-github](https://registry.coder.com/modules/coder/vault-github)** - Connect to Vault using GitHub authentication > > These modules work with both self-hosted Vault and HCP Vault Dedicated. For migration help, see the [official HashiCorp announcement](https://developer.hashicorp.com/hcp/docs/vault-secrets/end-of-sale-announcement). @@ -26,7 +26,7 @@ This module lets you fetch all or selective secrets from a [HCP Vault Secrets](h ```tf module "vault" { source = "registry.coder.com/coder/hcp-vault-secrets/coder" - version = "1.0.33" + version = "1.0.34" agent_id = coder_agent.example.id app_name = "demo-app" project_id = "aaa-bbb-ccc" @@ -52,7 +52,7 @@ To fetch all secrets from the HCP Vault Secrets app, skip the `secrets` input. ```tf module "vault" { source = "registry.coder.com/coder/hcp-vault-secrets/coder" - version = "1.0.33" + version = "1.0.34" agent_id = coder_agent.example.id app_name = "demo-app" project_id = "aaa-bbb-ccc" @@ -66,7 +66,7 @@ To fetch selective secrets from the HCP Vault Secrets app, set the `secrets` inp ```tf module "vault" { source = "registry.coder.com/coder/hcp-vault-secrets/coder" - version = "1.0.33" + version = "1.0.34" agent_id = coder_agent.example.id app_name = "demo-app" project_id = "aaa-bbb-ccc" @@ -81,7 +81,7 @@ Set `client_id` and `client_secret` as module inputs. ```tf module "vault" { source = "registry.coder.com/coder/hcp-vault-secrets/coder" - version = "1.0.33" + version = "1.0.34" agent_id = coder_agent.example.id app_name = "demo-app" project_id = "aaa-bbb-ccc"