villebro opened a new pull request, #167:
URL: https://github.com/apache/superset-kubernetes-operator/pull/167

   ## Summary
   
   Renames the `clone` lifecycle task to `seed` throughout the operator. 
"Clone" collides with database-operator semantics — in tools like CloudNativePG 
and Zalando, "clone" means restore-to-a-new-instance — and becomes ambiguous 
alongside the planned backup/restore feature. "Seed" describes what the task 
actually does: populating the metastore with a snapshot from an external 
source. This is a breaking CRD change, documented under `## Unreleased` in the 
changelog.
   
   ## Details
   
   **API (`api/v1alpha1`)**
   - `spec.lifecycle.clone` → `spec.lifecycle.seed`
   - Types `CloneTaskSpec`/`CloneSourceSpec` → `SeedTaskSpec`/`SeedSourceSpec`
   - Field `postCloneSQL` → `postSeedSQL`
   - Status `status.lifecycle.clone` → `.seed`; lifecycle phase `Cloning` → 
`Seeding`
   - CEL validation messages updated
   
   **Behavior / naming**
   - Task type `"Clone"` → `"Seed"`; Job name suffix `-clone` → `-seed`
   - Constants `CloneImage*` → `SeedImage*`; operator-internal env vars 
`SUPERSET_OPERATOR__CLONE_SRC_*` → `SUPERSET_OPERATOR__SEED_SRC_*`
   - All `*Clone*` funcs/vars → `*Seed*`; files `lifecycle_clone.go` → 
`lifecycle_seed.go`, `clone_test.go` → `seed_test.go`
   
   **Docs**
   - Updated user guide, architecture, security docs, and `AGENTS.md`
   - Added a `**Breaking:**` entry under `## Unreleased` in 
`docs/reference/releases.md`
   - Codified the breaking-change changelog convention (`**Breaking:**` marker) 
in `docs/contributing/development-guidelines.md`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to