Hello!
I'll preface this question with an admission of how basic it is - take it a little easy if you can (I'm just getting started).
My desired scenario is to build a workflow or series of workflows that will periodically refresh a small group of clones to match a certain master.
Chronologically, here's what happens:
1. Master VM is in desired state.
2. Clones 1-3 are created to match this master.
3. Done!
Here's the part that's getting bumpy for me - the second refresh.
Our desired behavior is this:
1. Old machines are destroyed and removed from disk.
2. New clones 1-3 created from updated master.
3. Done!
I want this to be automated as possible - that is, no other touching than kicking off a workflow.
The sticky part is when the first destruction is done. As a by-product of the outcome of that destruction workflow, the defined attribute (the box I want to destroy prior to rebuild) gets taken out of the workflow, so the next time I want to run it, shows 'not found' in the attribute.
Is there any way around this one?
Thanks for any info!