Epic Goal

Implement and enable the v1beta1 API for Shipwright.

Why is this important?

The v1beta1 API codifies features that the community considers stable, with stronger guarantees of support. This is important for productizing Shipwright, since GA-ed layered products come with implied support guarantees of at least 18 months per version (and perhaps longer).

The v1beta1 API also removes features that are deprecated in the v1alpha1 API. Encouraging use of the beta API will discourage use of deprecated features.

Upstream issues:

• https://github.com/shipwright-io/build/issues/1104
• https://github.com/shipwright-io/build/issues/1105
• https://github.com/shipwright-io/build/issues/1106

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. Upstream beta API proposal: SHIP-0035
2. Beta API workshop doc: https://hackmd.io/BsPjvGFwQgmVeJRe6FJfMA#Build-sources
3. Initial beta API implementation: https://github.com/shipwright-io/build/pull/1235

Open questions::

1. ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment