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

Allow unused resource in Pipelines 🎐 #1679

Merged
merged 1 commit into from
Dec 5, 2019

Conversation

vdemeester
Copy link
Member

Changes

We need to make sure the required resources are declared, but we
shouldn't error out in case of extras. A resource could be used only
in variable substitution (e.g. an image for the tag).

Signed-off-by: Vincent Demeester [email protected]

/cc @bobcatfish @piyush-garg

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.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Do not error out in case of extra, unused resource

We need to make sure the required resources are declared, but we
shouldn't error out in case of extras. A resource could be used only
in variable substitution (e.g. an image for the tag).

Signed-off-by: Vincent Demeester <[email protected]>
@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/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Dec 4, 2019
@ghost
Copy link

ghost commented Dec 4, 2019

/lgtm

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

ghost commented Dec 4, 2019

a unit test might be useful to ensure the expected behaviour for extras doesnt regress?

@ghost
Copy link

ghost commented Dec 5, 2019

@vdemeester if you want to follow-up with a unit test after this gets merged i'm also fine to approve this as-is. cancel hold if you wanna do that instead.

/hold
/approve

@tekton-robot tekton-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 5, 2019
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbwsg

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
@vdemeester
Copy link
Member Author

@sbwsg I can follow-up 😛
/hold cancel

@tekton-robot tekton-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 5, 2019
@tekton-robot tekton-robot merged commit 9389e37 into tektoncd:master Dec 5, 2019
@vdemeester vdemeester deleted the allow-unused-resource branch December 5, 2019 16:59
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/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants