@kbon I can't think of a use case either, but failing horribly and doing a very Wrong Thing if someone tries it is bad. Here's a horrible situation: I have two CIBs referenced in my manifests, `foo` and `bar`. Both also exist prior to the Puppet run. The resource that happens to get evaluated first has `cib => 'foo'` and works fine: Puppet refreshes the `foo` CIB and makes changes and commits it as desired. The other resource, the one with `cib => 'bar'`, also works, but Puppet fails to refresh the CIB first, and commits to the cluster some old configuration from three months ago when I was doing some testing. Whoops.