Don't enforce_idempotency

This is a nice idea in theory and a truly terrible one to my productivity
in practice: it makes 'kitchen converge' fail with hard to reason about
"resource changed" errors that involve resources such as
'directory[/etc/rabbitmq]'. Unless practically relevant
issues with recipe idempotency are found, I'd take a productive
development flow over hours spend troubleshooting
'kitchen converge' runs that are non-idempotent according
to the Chef resource change tracker.

Note that we do preserve multiple runs per convergence, which should
weed out obvious practical issues with non-idempotency of our recipes.

References #555.
parent 28307420
......@@ -12,7 +12,7 @@ transport:
provisioner:
name: dokken
multiple_converge: 2
enforce_idempotency: true
enforce_idempotency: false
# chef_log_level: debug
verifier:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment