-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Pipeline resource validation does not account for Condition resources #1263
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/kind bug |
I can propose a fix for this myself, but I want to make sure folks agree that this is a bug :) |
Yeah, I think this is a bug. I don't see a reason why we should limit the resources available to the condition to only the ones available to the task. |
/assign |
dibyom
added a commit
to dibyom/pipeline
that referenced
this issue
Sep 4, 2019
This commit fixes the Pipeline validation logic to account for resources that are declared in a `PipelineTaskCondition` but not in a `PipelineTask`. Previously, each resource used in a `PipelineTaskCondition` also had to be declared in the `PipelineTask`. Fixes tektoncd#1263 Signed-off-by: Dibyo Mukherjee <[email protected]>
3 tasks
dibyom
added a commit
to dibyom/pipeline
that referenced
this issue
Sep 4, 2019
This commit fixes the Pipeline validation logic to account for resources that are declared in a `PipelineTaskCondition` but not in a `PipelineTask`. Previously, each resource used in a `PipelineTaskCondition` also had to be declared in the `PipelineTask`. Fixes tektoncd#1263 Signed-off-by: Dibyo Mukherjee <[email protected]>
tekton-robot
pushed a commit
that referenced
this issue
Sep 4, 2019
This commit fixes the Pipeline validation logic to account for resources that are declared in a `PipelineTaskCondition` but not in a `PipelineTask`. Previously, each resource used in a `PipelineTaskCondition` also had to be declared in the `PipelineTask`. Fixes #1263 Signed-off-by: Dibyo Mukherjee <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
It should be possible to have resources only used by a
Condition
. For instance the following pipeline should be valid:Actual Behavior
Validation of the pipeline fails:
Steps to Reproduce the Problem
Additional Info
The
validateDeclaredResource
method inpipeline/pkg/apis/pipeline/v1alpha1/pipeline_validation.go
Lines 38 to 60 in 3950521
The text was updated successfully, but these errors were encountered: