Skip to content

taint / untaint

kyku taint <id> marks a resource already in state so the next kyku plan shows a replace (destroy + create), even when config matches the cloud. kyku untaint <id> clears that marker. The flag is stored on the state resource and survives save/load.

There is no --replace plan flag, no taint-by-tag/glob, and no cascade-taint.

Terminal window
kyku taint <id> [options]
kyku untaint <id> [options]
Flag Default Description
-e, --env <environment> default Environment workspace
Terminal window
# Force the next apply to rebuild this VM
kyku taint vm-web
# Change your mind
kyku untaint vm-web

Unknown ids exit 1 and list the ids currently in state. A timestamped state backup is written under .kyku/ before the file is mutated.

A successful apply of the replace writes the resource back without the taint marker.