Files
s3/weed/credential/validation_test.go
zooqueen dd74d3e6d6 Replace AGPL MinIO fork with Apache-2.0 SeaweedFS fork; rebrand CLI weed->s3
hanzoai/s3 was an AGPL-3.0 MinIO fork whose network-copyleft blocks embedding
and reselling as a managed service. Replace it wholesale with a fork of
SeaweedFS (github.com/seaweedfs/seaweedfs, Apache-2.0, Go) which ships a
built-in S3 gateway + Filer.

- License: AGPL-3.0 -> Apache-2.0 (upstream LICENSE kept verbatim, incl.
  "Copyright 2025 Chris Lu"); NOTICE added crediting SeaweedFS. No AGPL/BUSL/
  SSPL/GPL or enterprise ("ee") files remain.
- Module: go.mod path set to github.com/hanzoai/s3 with a self-replace
  (replace github.com/seaweedfs/seaweedfs => ./) so the ~1800 internal Go files
  keep their upstream import paths with zero churn. Internal identifiers and
  import paths are intentionally NOT renamed.
- CLI rebrand: the binary is built as `s3` (was `weed`); root usage, per-command
  help/usage/flag strings, shell autocomplete program name, and the product name
  in CLI output now read "Hanzo S3" / `s3`. Users never see `weed`.
  (e.g. `s3 server`, `s3 filer`, `s3 master`, `s3 volume`, `s3 s3`, `s3 mount`.)
- Build: `make` (or `go build -o s3 ./weed`) builds the `s3` binary green;
  `cmd/weed-db` and `cmd/weed-sql` also build; `go vet ./weed/command/` clean.
- README/LLM.md rewritten for Hanzo S3; AGENTS.md/CLAUDE.md symlinks preserved.
- Dropped a 33MB prebuilt Mach-O `stress` binary upstream had committed; `.gitignore`
  updated to ignore the `s3` build output.
2026-06-18 23:41:25 -07:00

50 lines
1.8 KiB
Go

package credential
import "testing"
func TestValidateServiceAccountId(t *testing.T) {
cases := []struct {
name string
id string
wantErr bool
}{
{"simple", "sa:alice:abcdef0123456789", false},
{"uppercase parent", "sa:ALICE:abcdef0123456789", false},
{"hyphenated uuid suffix", "sa:alice:123e4567-e89b-12d3-a456-426614174000", false},
{"with hyphen", "sa:test-user:abcdef0123456789", false},
{"with underscore", "sa:test_user:abcdef0123456789", false},
// AWS IAM usernames accept `+=,.@-` in addition to alphanumerics
// and underscore. Service account IDs must accept them too, or
// callers with realistic usernames hit a validation error at the
// persistence layer. See
// https://docs.aws.amazon.com/IAM/latest/APIReference/API_User.html
{"email-style", "sa:[email protected]:abcdef0123456789", false},
{"with dot", "sa:first.last:abcdef0123456789", false},
{"with plus", "sa:user+tag:abcdef0123456789", false},
{"with equals", "sa:user=prod:abcdef0123456789", false},
{"with comma", "sa:a,b:abcdef0123456789", false},
{"empty", "", true},
{"missing prefix", "alice:abcdef0123456789", true},
{"wrong prefix", "svc:alice:abcdef0123456789", true},
{"uppercase uuid", "sa:alice:ABCDEF0123456789", true},
{"missing uuid", "sa:alice:", true},
{"missing user", "sa::abcdef0123456789", true},
// Colon is not in the AWS IAM username set, and would break
// the colon-separated layout.
{"colon in user", "sa:a:b:abcdef0123456789", true},
}
for _, tc := range cases {
t.Run(tc.name, func(t *testing.T) {
err := ValidateServiceAccountId(tc.id)
if tc.wantErr && err == nil {
t.Fatalf("expected error for %q, got nil", tc.id)
}
if !tc.wantErr && err != nil {
t.Fatalf("unexpected error for %q: %v", tc.id, err)
}
})
}
}