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

   ## Summary
   
   - Redesigns the lifecycle trigger model: removes `Strategy` enum entirely, 
each task watches only its own specific inputs (clone→trigger/source, 
migrate→image, init→config), with automatic upstream propagation via a checksum 
chain.
   - Adds `Trigger *string` and `Disabled *bool` to `BaseTaskSpec` — all tasks 
get a manual force trigger and a disable switch.
   - Replaces the shared pipeline seed with per-task inputs anchored by 
parentUID. No more spurious re-runs from unrelated changes.
   
   ## Details
   
   **Trigger model:** Each task computes `hash(incomingChecksum, taskType, 
command, task-specific-inputs)`. The first task receives parentUID as anchor; 
each subsequent task receives its predecessor's completed status checksum. 
Universal rule: checksum match = skip, mismatch = execute.
   
   ```
   clone.checksum   = hash(parentUID,              "Clone",   cmd, {trigger, 
source, excludes})
   migrate.checksum = hash(clone.status.checksum,  "Migrate", cmd, {trigger, 
image})
   init.checksum    = hash(migrate.status.checksum, "Init",   cmd, {trigger, 
configChecksum})
   ```
   
   **What this fixes:**
   - Clone no longer re-runs on image/config changes (it only watches source 
config + trigger)
   - Config changes no longer trigger migrate (only init reacts to config)
   - Upstream propagation ensures consistency: clone re-run → migrate re-runs → 
init re-runs
   - Manual `trigger` on any task forces it + all downstream tasks
   
   **Strategy removal:** `VersionChange`/`Always`/`OnTrigger`/`Never` are gone. 
Trigger conditions are now implicit in what each task watches. `disabled: true` 
replaces `Strategy: Never`.


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