From 9dc9d25aa3351649521dd0ca7715e976896324c5 Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Mon, 24 Feb 2020 14:16:02 -0800 Subject: [PATCH] ci-operator/step-registry/ipi/ipi-workflow: Drop install-only workflow Job authors who need their own end-to-end test logic will need to define their own workflow, like a2fd8c3bfb (step-registry: add Origin E2E test step, 2020-01-31, #6965) did for origin-e2e. There's no way to piggy-back on a generic workflow to inject a custom test; but you can lean on existing pre and post chains. --- ci-operator/step-registry/ipi/ipi-workflow.yaml | 10 ---------- 1 file changed, 10 deletions(-) delete mode 100644 ci-operator/step-registry/ipi/ipi-workflow.yaml diff --git a/ci-operator/step-registry/ipi/ipi-workflow.yaml b/ci-operator/step-registry/ipi/ipi-workflow.yaml deleted file mode 100644 index 50bd4edd577f1..0000000000000 --- a/ci-operator/step-registry/ipi/ipi-workflow.yaml +++ /dev/null @@ -1,10 +0,0 @@ -workflow: - as: ipi - steps: - pre: - - ref: ipi-conf - - chain: ipi-install - post: - - chain: ipi-deprovision - documentation: |- - The IPI workflow provides pre- and post- steps that provision and deprovision an OpenShift cluster on a target IaaS platform, allowing job authors to inject their own end-to-end test logic.