You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cleanup resolved object before validating through dry-run
This ensure that we are not going to fail during validation with
dry-run. An example of such a failure would be the following scenario.
- A task in a namespace has `ownerReferences` with
`blockOwnerDeletion: true`
- A user uses the `cluster` resolver to fetch that task
- That user doesn't have a lot of rights in that namespace (only
listing Tasks for example).
/kind bug
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
(cherry picked from commit d3b18ea)
(cherry picked from commit a89b964)
// Verify the Pipeline once we fetch from the remote resolution, mutating, validation and conversion of the pipeline should happen after the verification, since signatures are based on the remote pipeline contents
// Verify the Task once we fetch from the remote resolution, mutating, validation and conversion of the task should happen after the verification, since signatures are based on the remote task contents
0 commit comments