Allow MarkDown files from a package to be used as manual intervention
Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.
I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.
However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the deployment.