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

Source release.yaml from GitHub release #208

Conversation

ayushsatyam146
Copy link
Contributor

Changes

The release.yaml used as the base for deploying Shipwright Builds appears to have been manipulated by a YAML linter or other processor. There are significant differentes in YAML structure and formatting between the kodata/release.yaml in tree and the release.yaml published on GitHub for the respective release (v0.12.0). This makes it difficult to verify that the operator is deploying the right thing, especially when versions are bumped.

This replaces the kodata/release.yaml in tree with the release.yaml published for v0.12.0. This will make it easy to verify that we are deploying the right version of Shipwright Builds with the operator, as well as support future workflows that let contributors update the deployed operand from a nightly release.

Fixes #184

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

NONE

The `release.yaml` used as the base for deploying Shipwright Builds
appears to have been manipulated by a YAML linter or other processor.
There are significant differentes in YAML structure and formatting
between the `kodata/release.yaml` in tree and the `release.yaml`
published on GitHub for the respective release (v0.12.0). This makes it
difficult to verify that the operator is deploying the right thing,
especially when versions are bumped.

This replaces the `kodata/release.yaml` in tree with the `release.yaml`
published for v0.12.0. This will make it easy to verify that we are
deploying the right version of Shipwright Builds with the operator, as
well as support future workflows that let contributors update the
deployed operand from a nightly release.

Signed-off-by: Ayush Satyam <[email protected]>
@pull-request-size pull-request-size bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label May 4, 2024
@openshift-ci openshift-ci bot requested review from adambkaplan and otaviof May 4, 2024 05:27
Copy link
Contributor

openshift-ci bot commented May 4, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign heavywombat 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:

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

@adambkaplan
Copy link
Member

@ayushsatyam146 Is this the same/exact content as #182 (just rebased?). I updated my original PR - with an additional commit that addressed an RBAC issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

[BUG] v0.12.0 does not ship an exact match of build v0.12.0
2 participants