Updates

Kratix supports updating Resource Requests with new specifications.

Given that the Resource workflows are defined within the parent Promise, updates to a Resource Request are limited to updating the request parameters in the spec.

Workflows

Any update to the Resource will result in Kratix re-running the Resource Configure workflow.

If a configure Pipeline is already running when the Resource is updated, Kratix waits for the current Job to reach a terminal state before restarting the workflow from the beginning.

Any files which are output by this workflow will replace all existing files associated with this Resource in the StateStore.

This workflow runs against the Promise Revision the Resource is currently bound to. Updating the request spec does not change that version. To reconcile a Resource against a different Promise version, update its Resource Binding — see the Upgrading a Promise guide.

Scheduling

If an update to a Resource changes its scheduling, the change will be ignored.

The Destination selected at the first the Workflow run is always used. To move a Resource from one Destination to another, you can delete and create it again.

See Managing Multiple Destinations for more details on scheduling.