[holoway]

This is a great question. Eventually, yes. In an earlier prototype of SI, we actually had this feature, and it was pretty dope. We removed it as we made things much more programmable, but it's high on the road map to bring back. The first will be an `import` function that just builds an individual component from a resource, followed by the full discovery feature.

[mst]

Naturally, what -I- really want is a three way diff between "the state SI thought production was in, the state SI has been asked to transition production to, and the state production is actually currently in."

I recall trying to convince you to experiment with that when you were building Chef but you'd just come out of working with finance stuff so understandably felt that an uncontrolled change should always be dealt with via emitting a resume generating event.

I continue to believe that for small non-bank organisations, when somebody gets paged in the middle of the night "whatever gets production to stop being on fire the fastest" is completely legitimate and systems automation tooling should support handling the config reconciliation -after- it's back up.

... but enjoy your launch day, having waited this long to argue my case again I can leave it a while longer :D