Skip to content

Tags: posinaga-demo/triggers

Tags

v0.5.0

Toggle v0.5.0's commit message
Add Support for Embedding TriggerBindingSpec in EL

TriggerBindingSpec can be added to EventListener Trigger

v0.4.0

Toggle v0.4.0's commit message
Fix incorrect split example

Also, adds a unit test that combines split and truncate.

Fixes tektoncd#518

Signed-off-by: Dibyo Mukherjee <[email protected]>

v0.4.0-rc1

Toggle v0.4.0-rc1's commit message
Bump pipeline version to 0.11.0

v0.3.1

Toggle v0.3.1's commit message
Resolve TriggerBindings with no Kind set in sink

When upgrading from 0.2.1 to 0.3, the Sink might have
to process a Binding that has no `Kind` set. This is
because, we only persist the default Kind when the Binding
object is created/updated. The reconciler also sets the defaults
by calling `SetDefaults` but that change is not persisted to etcd.

In the future, we might want to consider updating the object from the
reconciler itself if any default values were set.

Fixes: tektoncd#459

Signed-off-by: Dibyo Mukherjee <[email protected]>

v0.3.0

Toggle v0.3.0's commit message
Ensure Interceptor request uses HTTP POST.

Fixes tektoncd#437

v0.2.1

Toggle v0.2.1's commit message
Remove debug print statement in sink_test.go

Remove debug print statement in `sink_test.go`. Cleanup from PR
tektoncd#393.

v0.2.1-preview

Toggle v0.2.1-preview's commit message
Set upgrade context on webhook

This ensures that the automatic upgrades that we do in
`SetDefaults` (e.g. `binding` to `bindings`) are actually
persisted in etcd.

Previously we only did these upgrades on each reconcile
but did not persist them.

Signed-off-by: Dibyo Mukherjee <[email protected]>

v0.2.0

Toggle v0.2.0's commit message
Document exposing EL with openshift route

Added Openshift Route Doc for exposing eventlistener.
Also, modified command in existing document to get service name.

v0.1.0

Toggle v0.1.0's commit message
Introduce EventListener.Spec.ServiceType

Allows to set the type of the underlying eventlistener service.
If not set k8s will configure the service type to ClusterIP.

Depending on the cloud provider or the ingress controller used
the user might need to set the service type to `NodePort` or
`LoadBalancer` to expose it externally.