Author SHA1 Message Date
sneak 3aeb8f1cb6 Use a made-up host name in the secret-name test fixture (closes #200)
check / check (push) Successful in 2m41s
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
2026-11-16 05:57:01 +00:00
2 changed files with 5 additions and 1 deletions

No files matched your search

+4
View File
@@ -17,6 +17,10 @@ https://git.eeqj.de/sneak/secret/milestone/12
# Completed Steps
- 2026-11-16: The example secret name in `internal/vault/secrets_name_test.go`
no longer contains the name of a real server
(https://git.eeqj.de/sneak/secret/issues/200). It uses the made-up `host1`
instead.
- 2026-10-15: The comment on `commandWait` in `internal/cli/integration_test.go`
no longer says `script/test` gives the package 30 seconds
(https://git.eeqj.de/sneak/secret/issues/195). `script/test` sets no time
+1 -1
View File
@@ -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},