Comment 6 for bug 1513220

from shardy on irc:

12:17 < shardy> slagle: Ok, well the data used as an input to heat-config is still there (the heat metadata asociated with the server), so it must be possible to re-created some dummy deployments data
12:19 < shardy> https://github.com/openstack/tripleo-image-elements/blob/master/elements/os-refresh-config/os-refresh-config/post-configure.d/99-refresh-completed#L66
12:19 < shardy> e.g a loop like that which touches the file and stops heat-config running
12:19 * shardy checks what heat-config expects
12:20 < shardy> slagle: I think it's just checking for <deployment_id>.json
12:20 < shardy> so a loop touching the files is probably enough

I think this could work. We just need something so that the deployments are not re-applied if they've already been lost/deleted.