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

Move image data extraction into entrypoint_lookup.go #1686

Merged
merged 1 commit into from
Dec 5, 2019

Conversation

imjasonh
Copy link
Member

@imjasonh imjasonh commented Dec 4, 2019

Image data extraction (pulling entrypoint and digest) isn't specific to
the real implementation of fetching image metadata using K8s
imagePullSecrets, so having this only implemented and tested in that
context didn't make sense.

This change also adds cache population (Set) moved into the
EntrypointCache interface, rather than having it be a side effect of
Get. This means that entrypoint_lookup.go must call cache.Set after it
extracts digest.

The result is a cleaner separation of concerns between generic
entrypoint lookup logic and K8s-specific implementation, which is now
more narrowly scoped.

More iteration on #1605

Ideally this separation and testing would have helped catch #1674

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Image data extraction (pulling entrypoint and digest) isn't specific to
the real implementation of fetching image metadata using K8s
imagePullSecrets, so having this only implemented and tested in that
context didn't make sense.

This change also adds cache population (Set) moved into the
EntrypointCache interface, rather than having it be a side effect of
Get. This means that entrypoint_lookup.go must call cache.Set after it
extracts digest.

The result is a cleaner separation of concerns between generic
entrypoint lookup logic and K8s-specific implementation, which is now
more narrowly scoped.
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Dec 4, 2019
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 4, 2019
@ghost
Copy link

ghost commented Dec 5, 2019

/lgtm

@tekton-robot tekton-robot assigned ghost Dec 5, 2019
@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2019
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

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

Nice 😻
/lgtm
/meow

@tekton-robot
Copy link
Collaborator

@vdemeester: cat image

In response to this:

Nice 😻
/lgtm
/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@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 Dec 5, 2019
@tekton-robot tekton-robot merged commit fc1658c into tektoncd:master Dec 5, 2019
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. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants