Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate alpha features #1111

Merged

Conversation

adambkaplan
Copy link
Member

Changes

Deprecate the following features from Shipwright Build:

  • spec.sources in Build (multiple sources and HTTP artifact downloads)
  • status in Build (controller validations for Build objects)
  • spec.dockerfile in Build (provide path to Dockerfile)
  • spec.builder in Build (provide builder image for s2i builds)
  • spec.serviceaccount.generate in BuildRun (generated service accounts)

/kind cleanup

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

The following features are deprecated: 1) Multiple sources for builds, 2) HTTP artifact downloads, 3) Status validations for `Builds`, 4) Providing a builder image in a `Build`, 5) Providing the path to a Dockerfile in a `Build`, 6) Generating service accounts in a `BuildRun`.

This deprecates the `spec.sources` field, thereby deprecating the
"remote artifact" download feature. Per discussion in the Beta API
workshop, this feature will be removed from Shipwright once the beta
API reaches stability.
Deprecate the build status subobject. This will be removed in the beta
API.
Deprecate the following fields in the `Build` spec object:

- `builder` - this is specific to source-to-image.
- `dockerfile` - this is specific to Dockerfile-based tools.
Deprecate the generated service account behavior. This feature will
eventually be removed from Shipwright.
@openshift-ci openshift-ci bot added release-note Label for when a PR has specified a release note kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Sep 7, 2022
@adambkaplan
Copy link
Member Author

/assign @SaschaSchwarze0

Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

Comment on lines 120 to +122
// +optional
//
// NOTICE: Multiple sources in a build are deprecated. This feature will be removed in a future release.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems to work based on what I see being generated. For consistency, I would always have the "annotations" at the end.

Suggested change
// +optional
//
// NOTICE: Multiple sources in a build are deprecated. This feature will be removed in a future release.
// NOTICE: Multiple sources in a build are deprecated. This feature will be removed in a future release.
//
// +optional

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 7, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 7, 2022
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.11.0 milestone Sep 7, 2022
@SaschaSchwarze0 SaschaSchwarze0 added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Sep 7, 2022
@SaschaSchwarze0
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 8, 2022
@openshift-merge-robot openshift-merge-robot merged commit 4c5a50b into shipwright-io:main Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants