From e916c5347b98b79d5396d917b83c1fc11a57b68f Mon Sep 17 00:00:00 2001 From: clawbot <35+clawbot@noreply.example.org> Date: Mon, 16 Nov 2026 07:55:40 +0100 Subject: [PATCH] Use a made-up host name in the secret-name test fixture (closes #200) The example secret name in the uppercase-name test contained the name of one of our servers. It now uses host1; the rest of the name, including the uppercase key ID, is unchanged. Model: opus-5-5 --- internal/vault/secrets_name_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/vault/secrets_name_test.go b/internal/vault/secrets_name_test.go index 7218c55..502279f 100644 --- a/internal/vault/secrets_name_test.go +++ b/internal/vault/secrets_name_test.go @@ -19,7 +19,7 @@ func TestIsValidSecretNameUppercase(t *testing.T) { // Uppercase (new behavior - issue #2) {"Valid-Upper-Name", true}, - {"2025-11-21-ber1app1-vaultik-test-bucket-AKI", true}, + {"2025-11-21-host1-vaultik-test-bucket-AKI", true}, {"MixedCase/Path/Name", true}, {"ALLUPPERCASE", true}, {"ABC123", true},