Now that we're calling tripleo-common with a manifest for the DIB invocation, we should wrap it in a bash jinja template, so debugging is simple / clear. Presently it's a PITA to debug things when they fail. It helps to keep the temp files around and debug in that fashion, but unlike the other steps there are no .sh artifacts that will reproduce a failed step (the actual tripleo-common call).
Now that we're calling tripleo-common with a manifest for the DIB invocation, we should wrap it in a bash jinja template, so debugging is simple / clear. Presently it's a PITA to debug things when they fail. It helps to keep the temp files around and debug in that fashion, but unlike the other steps there are no .sh artifacts that will reproduce a failed step (the actual tripleo-common call).