ci-operator/step-registry/openshift/kubernetes/e2e/aws: Include "aws" in workflow name

[wking]

It's an AWS workflow, and we might grow additional workflows for other platforms in the future. Including the platform in the workflow name makes space for that, and sets the stage for automated tooling that can rebalance between platforms by shifting load from openshift-kubernetes-e2e-aws to openshift-kubernetes-e2e-gcp, or whatever.

[openshift-ci-robot]

@wking: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/rehearse/openshift/kubernetes/master/kubernetes-e2e	3312062	link	/test pj-rehearse
ci/prow/pj-rehearse	3312062	link	/test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/OWNERS [petr-muller]
• ci-operator/step-registry/openshift/kubernetes/OWNERS [petr-muller,wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@wking: Updated the following 3 configmaps:

• step-registry configmap in namespace ci at cluster app.ci using the following files:
  • key OWNERS using file ci-operator/step-registry/openshift/kubernetes/e2e/aws/OWNERS
  • key openshift-kubernetes-e2e-workflow.yaml using file ``
  • key openshift-kubernetes-e2e-aws-workflow.yaml using file ci-operator/step-registry/openshift/kubernetes/e2e/aws/openshift-kubernetes-e2e-aws-workflow.yaml
• step-registry configmap in namespace ci at cluster api.ci using the following files:
  • key OWNERS using file ci-operator/step-registry/openshift/kubernetes/e2e/aws/OWNERS
  • key openshift-kubernetes-e2e-workflow.yaml using file ``
  • key openshift-kubernetes-e2e-aws-workflow.yaml using file ci-operator/step-registry/openshift/kubernetes/e2e/aws/openshift-kubernetes-e2e-aws-workflow.yaml
• ci-operator-master-configs configmap in namespace ci at cluster app.ci using the following files:
  • key openshift-priv-kubernetes-master.yaml using file ci-operator/config/openshift-priv/kubernetes/openshift-priv-kubernetes-master.yaml
  • key openshift-kubernetes-master.yaml using file ci-operator/config/openshift/kubernetes/openshift-kubernetes-master.yaml

Details

In response to this:

It's an AWS workflow, and we might grow additional workflows for other platforms in the future. Including the platform in the workflow name makes space for that, and sets the stage for automated tooling that can rebalance between platforms by shifting load from openshift-kubernetes-e2e-aws to openshift-kubernetes-e2e-gcp, or whatever.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.