Story (Required)

As a developer trying to build applications with Shipwright I want the upstream tests to reference the Beta APIs.

Background (Required)

• Developers are unable to test new code that utilizes the v1beta1 API.
•  https://github.com/shipwright-io/build/issues/1373 

Out of scope

 - None

Approach (Required)

• Using grep (or a similar IDE based solution) search for any references to the `v1alpha1` API in any of the code repositories under the shipwright-io github organization.
• Run the unit, e2e and integration tests locally, fixing any issues caused by the API changes.

Dependencies

• The v1beta1 API pull request needs to be merged into the shipwright-io/build repository OR that code needs to be rebased into the developers feature branch and test images built and deployed locally for the tests to pass.

Acceptance Criteria (Mandatory)

1. No references are made to the v1alpha1 API in test code except for a suite of tests that exercises the round tripping of the v1alpha1 -> v1beta1 -> v1alpha1 conversion functionality.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met