Skip to content
New issue

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

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

Already on GitHub? # to your account

Move Resolution bundle, git, and hub resolver pkgs over #5384

Merged
merged 1 commit into from
Aug 26, 2022

Conversation

abayer
Copy link
Contributor

@abayer abayer commented Aug 26, 2022

Changes

Part of #4710

pkg/resolution/resolver/bundle/bundle.go is rewritten here based on pkg/remote/oci/resolver.go. This is cleaner code than the original, and retains the original Pipeline bundle resolution behavior of falling back to reading layers as raw if there were errors in reading them as tarballs, rather than only reading layers as raw if there's no matching digest.

/kind feature

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Part of tektoncd#4710

`pkg/resolution/resolver/bundle/bundle.go` is rewritten here based on `pkg/remote/oci/resolver.go`. This is cleaner code than the original, and retains the original Pipeline bundle resolution behavior of falling back to reading layers as raw if there were errors in reading them as tarballs, rather than only reading layers as raw if there's no matching digest.

Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
@abayer abayer added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 26, 2022
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Aug 26, 2022
@tekton-robot tekton-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 26, 2022
@abayer
Copy link
Contributor Author

abayer commented Aug 26, 2022

/assign @lbernick @jerop @dibyom @vdemeester

@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/resolution/resolver/bundle/bundle.go Do not exist 0.0%
pkg/resolution/resolver/bundle/params.go Do not exist 75.9%
pkg/resolution/resolver/bundle/resolver.go Do not exist 25.0%
pkg/resolution/resolver/git/resolver.go Do not exist 84.1%
pkg/resolution/resolver/hub/resolver.go Do not exist 65.0%

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 26, 2022
@lbernick
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 26, 2022
@tekton-robot tekton-robot merged commit bdcc051 into tektoncd:main Aug 26, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants