Decouple from Pipeline or Align with Pipeline release

[khrm]

Expected Behavior

Whenever a new pipeline is released, tkn-cli should have no problem in updating to it and at the same time using Triggers.

Actual Behavior

At present, this causes a dependency issue at tkn-cli side. We need to update Pipeline in Triggers before in tkn-cli.

Additional Info

Either decoupling or aligning Triggers with Pipeline release would solve this issue.

[dibyom]

/area dependency

[dibyom]

The main usage of pipeline in triggers is the the Param type. Maybe we don't need to reuse param...I don't think we are using ArrayParams anyway!

[dibyom]

For the 0.3 release, we decided that I can co-ordinate with CLI/Pipeline to ensure we have the pipeline version we need

[vtereso]

We can close this issue/readdress once we sync in 0.4.

[vdemeester]

@vtereso how so ? this will be an issue after 0.4 right ?
@dibyom if it's only for Param types, it might be worth "duplicating" those (acting like a completely separate client, using the API only, no shared code)

[ncskier]

@dibyom if it's only for Param types, it might be worth "duplicating" those (acting like a completely separate client, using the API only, no shared code)

I agree with @vdemeester that it shouldn't be a problem to create our own Param types.

---

Trying to create a quick summary, currently I think we use Pipelines for:

• tests
• Params
• clientset for creating resources (the two files mentioned in this issue)

Is there anything else that I'm missing?

[dibyom]

I think that's about it

[dibyom]

I like Vincent's idea though I think this can wait till 0.5.

[dibyom]

/assign

[dibyom]

I found one other usage of Params (incl. ArrayParams): Header values in webhook interceptor. Though I'm wondering if we can always use []string like Go header values instead of arrayOrString.

[ncskier]

Another option is to use Go's http Header type.
Although, that's a map[string][]string, so it would change the interceptor YAML syntax a bit.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.