chef - test-kitchen update instead of create everytime -


in test-kitchen, there way update instance created instead of destroying , recreating instance everytime? if change in kitchen.yml , want see change, running whole destroy/create can take while.

depending on provider using - yes.

first, there few lifecycle steps:

  1. kitchen create - create instance. it's equivalent of vagrant --no-provision.
  2. kitchen converge - converge (provision) instance. it's equivalent of vagrant provision.
  3. kitchen verify - run post-integration tests (like serverspec or bats). there no equivalent in vagrant.
  4. kitchen test - wraps above 3 commands in single sequence.

test kitchen not have notion of vagrant reload, seem describe example. however, can accomplish reload doing like:

cd .kitchen/suite_name && vagrant reload 

from command line.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -