Tekton Triggers v0.2.1

-Docs @ v0.2.1
-Examples @v0.2.1

Fixes

• Fix interceptor panic (#357)
• Allow brackets in TriggerBinding expressions (#376)
• Fix crashloop when upgrading EventListeners from 0.1 to 0.2 (#369)
• Disallow non label compliant names for Triggers (#383)
• Fix bug running multiple Triggers (#388)
• Fix webhook Interceptor header bug #393 (#399)

Upgrading from v0.1.0

1. Give any ServiceAccount used by an EventListener permission to get, list, and watch ConfigMaps. If you are using GitHub/GitLab interceptors to do payload verification, the ServiceAccount needs get on Secrets as well.
2. Update TriggerBindings to use JSONPath syntax instead of gjson syntax.
3. Move any EventListener params into a TriggerBinding.
4. Update EventListener Interceptors to use the Webhook Interceptor syntax.
5. Update any trigger names or EventListener names that do not adhere to the Kubernetes syntax and character set requirements for label values.

Thanks

Thanks to these contributors who contributed to v0.2.1!

• @afrittoli
• @chmouel
• @dibyom
• @mattmoor
• @ncskier

[DRAFT] Tekton Triggers v0.2.1-preview

Fixes

• Fix interceptor panic
• Allow nested brackets in TriggerBinding expressions
• Fix crashloop when upgrading ELs from 0.1 to 0.2
• Fix webhookInterceptor Bug
• Disallow non label compliant names for Triggers

Upgrading from v0.1.0

1. Give any ServiceAccount used by an EventListener permission to get, list, and watch ConfigMaps. If you are using Github/Gitlab interceptors to do payload verification, the ServiceAccount needs get on Secrets as well.
2. Update TriggerBindings to use JSONPath syntax instead of gjson syntax.
3. Move any EventListener params into a TriggerBinding.
4. Update EventListener Interceptors to use the Webhook Interceptor syntax.
5. Update any trigger names or EventListener names that do not adhere to the Kubernetes syntax and character set requirements for label values.

Tekton Triggers v0.2.0

Tekton Triggers v0.2.0

Head over to the docs to get started:
https://github.com/tektoncd/triggers/tree/v0.2.0#tekton-triggers and https://github.com/tektoncd/triggers/tree/v0.2.0/docs

Notable Changes

• Interceptors - Triggers now support user configurable interceptors to allow modification and filtering of events. Included in this release are the following interceptors:
  • GitHub: Allows for validation of GitHub webhooks
  • GitLab: Allows for validation of GitLab webhooks
  • CEL: Allows for user configurable filtering expressions based on the incoming event payload. See https://opensource.google/projects/cel for more details.
  • Webhook: Allows for user configurable interceptor extensions by calling out to the configured Kubernetes Service.
• Resources generated by Triggers are labelled with the trigger name, EventListener name, and event ID.
• Triggers now support multiple TriggerBindings.
• TriggerBindings now use JSONPath query syntax.
• EventListeners support dynamic clients to allow creation of custom resources.
• EventListeners return JSON responses including trace information.
• EventListener pods use a logger configured by a ConfigMap.

Breaking Changes

• gjson syntax for TriggerBindings was removed in favor of JSONPath.
• EventListenerTrigger.params is removed in favor of multiple bindings.
• Trigger names and EventListener names must adhere to the Kubernetes syntax and character set requirements for label values.

Deprecation Warnings

• EventListenerTrigger.interceptor is deprecated in favor of interceptors.
• EventListenerTrigger.binding is deprecated in favor of bindings.

Upgrading from v0.1.0

1. Give any ServiceAccount used by an EventListener permission to get, list, and watch ConfigMaps. If you are using Github/Gitlab interceptors to do payload verification, the ServiceAccount needs get on Secrets as well.
2. Update TriggerBindings to use JSONPath syntax instead of gjson syntax.
3. Move any EventListener params into a TriggerBinding.
4. Update EventListener Interceptors to use the Webhook Interceptor syntax.
5. Update any trigger names or EventListener names that do not adhere to the Kubernetes syntax and character set requirements for label values.

Thanks

Thanks to these contributors who contributed!

@afrittoli
@akihikokuroda
@bigkevmcd
@bobcatfish
@CarolynMabbott
@castlemilk
@cccfeng
@chmouel
@dibyom
@dlorenc
@Fabian-K
@iamejboy
@imjasonh
@khrm
@mattmoor
@ncskier
@nvoskuilen
@piyush-garg
@soulseen
@ston1th
@vdemeester
@vtereso
@wlynch
@zhangtbj

Tekton Triggers release v0.1.0

🎉 First Tekton Triggers Release! 🎉

This is the very first release of Tekton Triggers, which has built on the original tekton listener design, allowing users to extract information from events payloads (a "trigger") to create Kubernetes resources.

Head over to the docs to get started: https://github.com/tektoncd/triggers/tree/v0.1.0#tekton-triggers and https://github.com/tektoncd/triggers/tree/v0.1.0/docs

Features

• TriggerTemplate - Templates resources to be created (e.g. Create PipelineResources and PipelineRun that uses them)

• TriggerBinding - Validates events and extracts payload fields

• EventListener - Connects TriggerBindings and TriggerTemplates into an addressable endpoint (the event sink). It uses the extracted event parameters from each TriggerBinding (and any supplied static parameters) to create the resources specified in the corresponding TriggerTemplate. It also optionally allows an external service to pre-process the event payload via the interceptor field.

Thanks

Thanks to these contributors who contributed!

• @akihikokuroda
• @a-roberts
• @wlynch
• @ncskier
• @bobcatfish
• @dibyom
• @EliZucker
• @iancoffey
• @eonpatapon
• @khrm
• @vincent-pli
• @shuheiktgw
• @vdemeester
• @vtereso