sanitize.go RawHistoryFolder

1package domain
2
3import (
4	"crypto/sha256"
5	"fmt"
6	"strings"
7)
8
9// SanitizeDomainForContainer makes a domain safe for container naming.
10// It uses distinct replacements to avoid collisions between domains like
11// "git.example.com" and "git-example.com" (which would both become "git-example-com"
12// if we naively replaced all separators with hyphens).
13//
14// Replacements:
15//
16//	. → __ (double underscore, distinct from single _ in some conventions)
17//	: → -_ (hyphen-underscore combo, used for ports)
18//	/ → -- (double hyphen, distinct from colon to avoid :/ collisions)
19func SanitizeDomainForContainer(domain string) string {
20	result := strings.ReplaceAll(domain, ".", "__")
21	result = strings.ReplaceAll(result, ":", "-_")
22	result = strings.ReplaceAll(result, "/", "--")
23	return result
24}
25
26// StableResourceName returns a Docker-safe, collision-resistant name fragment.
27func StableResourceName(value string) string {
28	digest := sha256.Sum256([]byte(value))
29	return fmt.Sprintf("%s-%x", SanitizeDomainForContainer(value), digest[:6])
30}
31
32// SanitizeDomainForContainerLegacy uses the OLD (buggy) sanitization that replaces
33// all separators with hyphens, for backwards compatibility.
34//
35// IMPORTANT: This is maintained ONLY for finding old containers during upgrades.
36// New containers always use the collision-resistant SanitizeDomainForContainer().
37//
38// Migration strategy:
39// - During binary upgrades, legacy containers are found using this function
40// - Old containers are stopped and removed, then replaced with new containers
41// - New containers use the collision-resistant SanitizeDomainForContainer() naming
42// - After all deployments are upgraded, this function can be removed in a major version
43func SanitizeDomainForContainerLegacy(domain string) string {
44	result := strings.ReplaceAll(domain, ".", "-")
45	result = strings.ReplaceAll(result, ":", "-")
46	result = strings.ReplaceAll(result, "/", "-")
47	return result
48}