unkin-agent
9da206dc7c
PVCs and CloudNativePG Clusters need S3 buckets and backup schedules
provisioned consistently. This operator watches the
backups.unkin.net/{schedule,destination} annotations on those objects and
provisions everything needed to back them up, with no new CRDs.
- Add a PVC controller that provisions cephrgw ObjectStoreUser/Bucket/BucketAccess,
auto-generates a restic repo-password Secret and creates a k8up Schedule scoped
to the PVC via spec.backup.volumes[].persistentVolumeClaim.claimName.
- Add a CNPG Cluster controller that provisions the same bucket stack, idempotently
patches spec.backup.barmanObjectStore (leaving a user-set destinationPath alone
with a Warning event) and creates a ScheduledBackup.
- Resolve destinations through a ConfigMap lookup table; requeue until the
BucketAccess is Ready before creating schedule resources; own-reference created
resources and retain bucket data by default.
- Add schedule-mapping helpers (k8up 5-field/shortcut pass-through, CNPG 6-field
seconds-first) and deterministic, length-bounded name derivation.
- Add unit tests (schedule mapping, name derivation, destination resolution) and
envtest controller tests for both paths, wiring the external CRDs into envtest.
- Add kubebuilder-generated RBAC, a Dockerfile (distroless/nonroot), Woodpecker
lint/test/build pipelines and a tag-triggered image push to the artifactapi
docker-internal registry, plus a version-bump Makefile and deploy manifests.
26 lines
1010 B
Go
26 lines
1010 B
Go
// SPDX-FileCopyrightText: Copyright 2015-2025 go-swagger maintainers
|
|
// SPDX-License-Identifier: Apache-2.0
|
|
|
|
// Package mangling provides name mangling capabilities.
|
|
//
|
|
// Name mangling is an important stage when generating code:
|
|
// it helps construct safe program identifiers that abide by the language rules
|
|
// and play along with linters.
|
|
//
|
|
// Examples:
|
|
//
|
|
// Suppose we get an object name taken from an API spec: "json_object",
|
|
//
|
|
// We may generate a legit go type name using [NameMangler.ToGoName]: "JsonObject".
|
|
//
|
|
// We may then locate this type in a source file named using [NameMangler.ToFileName]: "json_object.go".
|
|
//
|
|
// The methods exposed by the NameMangler are used to generate code in many different contexts, such as:
|
|
//
|
|
// - generating exported or unexported go identifiers from a JSON schema or an API spec
|
|
// - generating file names
|
|
// - generating human-readable comments for types and variables
|
|
// - generating JSON-like API identifiers from go code
|
|
// - ...
|
|
package mangling
|