Create a Mistral action to inject default plan files

[Dan Prince]

Some downstream uses would like a place in our Mistral workflow to inject downstream default environments by default. This would allow users to add custom environment files that differ with regards to upstream TripleO in an easy to maintain format.

[Julie Pichon (jpichon)]

I don't have an environment stable enough to test this at the moment but I wonder if simply updating plan-environment.yaml [1] directly would work? I see we have overcloud-resource-registry-puppet.yaml in there already, doesn't that mean this is a "default" environment, always enabled already?

[1] https://github.com/openstack/tripleo-heat-templates/blob/master/plan-environment.yaml#L7

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/537402

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/537405

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.openstack.org/537402

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dan Prince (<email address hidden>) on branch: master
Review: https://review.openstack.org/537405
Reason: Ditching this in favor of plan environment.

[Alex Schultz (alex-schultz)]

Do we still need this bug? It looks like the patches are abandoned and there may be an alternative way to handle this. I'm moving this bug back to Triaged, but please close it if it is not valid.

[Julie Pichon (jpichon)]

Right, this was handled by modifying plan-environment.yaml directly in the end so there was/is no need for extra code at this point.