Christie Warwick (Wilson)

Hey @jpower432 - our workaround is just to pin to alpine 3.11 https://github.com/tektoncd/pipeline/pull/2757 This works for us because we didn't have any particular need to use 3.12 but won't work...

Hi all! In the Tekton community we have some discussion on the parameterless question as well (some notes [in this doc on SLSA + Tekton](https://docs.google.com/document/d/12yYP0M_zz5Tc9ftGnLwhDZ_tdZBq4mEod70ngWtHmLs/edit#heading=h.80wkb4xgt55l), shared with [email protected] and [email protected]))...

> GCB and Tekton allow the build script to be defined via the UI, not coming from the source repo. Small detail re Tekton: the hurdle for Tekton is that...

+1 to this question - from a Tekton perspective we are wondering about how to meet this requirement as well. Without disallowing network access it seems unreasonable to verify that...

@mrutkows if it was possible to specify the supporting Tasks [via their location in an OCI registry](https://github.com/tektoncd/community/blob/master/teps/0005-tekton-oci-bundles.md), would you still need something like deploy.sh? (cuz in this case you wouldn't...

I think we know we want this in the long run - and we already have 1 pipeline! so: /lifecycle frozen

I think we still need to make some decisions here, particularly since we have tasks that now rely on pipelineresource images - if we phase out pipelineresources and/or completely change...

Ah interesting idea! So you'd like a way to _trigger_ the creation of the resources in the `TriggerTemplate` arbitrarily by providing the values you need 🤔 I think this is...

This is in the project roadmap https://github.com/tektoncd/triggers/blob/master/roadmap.md /lifecycle frozen

/remove-lifecycle rotten @dibyom do you think this makes sense to include in the roadmap?