Skip to content

feat: limit resource deletion on trigger#6754

Open
Jaakkonen wants to merge 1 commit intotilt-dev:masterfrom
Jaakkonen:feat/trigger-safety
Open

feat: limit resource deletion on trigger#6754
Jaakkonen wants to merge 1 commit intotilt-dev:masterfrom
Jaakkonen:feat/trigger-safety

Conversation

@Jaakkonen
Copy link
Copy Markdown
Contributor

Currently if tilt trigger is run on a resource with RBACs, admission webhooks or ServiceAccounts those are removed causing cascading failures on other resources with resource_deps to them.

This commit changes the tilt trigger logic to not call ForceDelete on this kind of resources while keeping for example Jobs and Pods in the scope of ForceDelete for faster development loops.

Currently if `tilt trigger` is run on a resource with RBACs, admission webhooks or ServiceAccounts
those are removed causing cascading failures on other resources with `resource_deps` to them.

This commit changes the `tilt trigger` logic to not call ForceDelete on this kind of resources while
keeping for example `Job`s and `Pod`s in the scope of ForceDelete for faster development loops.

Signed-off-by: Jaakko Sirén <jaakko@craci.com>
@Jaakkonen Jaakkonen force-pushed the feat/trigger-safety branch from d30cffb to 0eb018b Compare April 26, 2026 12:37
@Jaakkonen Jaakkonen marked this pull request as ready for review May 5, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant