NO-JIRA: Rename efscreate package

[stephenfin]

Align with the name of the binary as is done for everything else.

Signed-off-by: Stephen Finucane [email protected]

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stephenfin
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[stephenfin]

/retitle: NO-JIRA: Rename efscreate package

[openshift-ci-robot]

@stephenfin: This pull request explicitly references no jira issue.

In response to this:

Align with the name of the binary as is done for everything else.

Signed-off-by: Stephen Finucane [email protected]

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 openshift-eng/jira-lifecycle-plugin repository.

[gnufied]

I think if we do this, we will have to update how we run e2e tests for efs driver too in openshift/release repo.

[openshift-ci]

@stephenfin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-upgrade	beb225a	link	true	/test e2e-aws-ovn-upgrade
ci/prow/e2e-openstack-cinder-csi	beb225a	link	true	/test e2e-openstack-cinder-csi
ci/prow/hypershift-aws-e2e-external	beb225a	link	true	/test hypershift-aws-e2e-external
ci/prow/e2e-azure-file-csi	beb225a	link	true	/test e2e-azure-file-csi
ci/prow/e2e-azurestack-csi	beb225a	link	false	/test e2e-azurestack-csi
ci/prow/e2e-openstack-manila-csi	beb225a	link	true	/test e2e-openstack-manila-csi

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.