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

   ## Summary
   
   After #173 the operator no longer reasons about semantic versions — it 
triggers an idempotent `superset db upgrade` whenever the resolved image 
**tag** changes byte-for-byte, and nothing else. The lingering "version" 
nomenclature in the API is therefore misleading: `status.version` is populated 
straight from `spec.image.tag` (it's the tag, not a version) and drives a 
`kubectl get` column labeled "Version", and 
`status.lifecycle.upgrade.fromVersion`/`toVersion` likewise hold tags.
   
   This PR renames that surface to "tag" so the API matches what the code 
actually does. It is a pure rename with no behavior change.
   
   **Breaking change** (still v0): `status.version` → `status.tag` (the 
`kubectl get` column is renamed Version → Tag), and 
`status.lifecycle.upgrade.fromVersion` / `toVersion` → `fromTag` / `toTag`.
   
   ## Details
   
   - `SupersetStatus.Version` → `Tag`; `UpgradeContext.FromVersion`/`ToVersion` 
→ `FromTag`/`ToTag`, with doc comments; printer column updated.
   - Rename references in `status.go`, `lifecycle.go` (`checkUpgradeGates` 
literal, the AwaitingApproval message, and `upgradeContextMatches` params).
   - Update unit tests and the e2e supervised-upgrade JSONPaths.
   - Fix a stale `MigrateTaskSpec` comment and the `internals.md` status 
example.
   - Regenerate CRDs, Helm CRDs, and the API reference via `make codegen`; add 
an Unreleased changelog entry.


-- 
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