Comment 2 for bug 1463092

The problem with (3) AFAICS is that even if we reapply the manifest when the digest changes, we have lost the ability to signal back to heat if that apply fails. Or are you suggesting that the Deployment creating the hieradata would fail as it cascades and applies all-the-manifests on update?

That's why I'm preferring (2) so we create an explicit dependency inside the templates, which should mean all deployment resources actually see an update when the hieradata changes, thus we enter the normal update cycle and potentially get more granular feedback about what actually failed in the event some manifest apply falls over with the new values?