Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated values of TriggerTemplate and TriggerBinding not getting reflected in EventListener #1036

Closed
VeereshAradhya opened this issue Apr 9, 2021 · 2 comments · Fixed by #1037
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@VeereshAradhya
Copy link

VeereshAradhya commented Apr 9, 2021

Expected Behavior

Updated values of TriggerTemplate and TriggerBinding should get reflected in EventListener

Actual Behavior

Updated values of TriggerTemplate and TriggerBinding not getting reflected in EventListener

Steps to Reproduce the Problem

  1. Create TriggerTemplate, TriggerBinding, Trigger and EventListener and bind them
  2. Change the name of the resource in created TriggerTemplate
  3. Trigger an event and observe if there is any change in the resource created by eventListener

cc: @savitaashture

Additional Info

  • Kubernetes version:

    Output of kubectl version:

    $ kubectl version
    Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"5797eaecac19b9c0e4d10d3d6b559c074e3c3c88", GitTreeState:"clean", BuildDate:"2021-01-27T07:28:48Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
    Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0+bafe72f", GitCommit:"bafe72fb05eddc8246040b9945ec242b9f805935", GitTreeState:"clean", BuildDate:"2021-03-14T16:01:39Z", GoVersion:"go1.15.7", Compiler:"gc", Platform:"linux/amd64"}
    
  • Tekton Pipeline version:

$ tkn version
Client version: 0.17.1
Pipeline version: v0.22.0
Triggers version: main
@VeereshAradhya VeereshAradhya added the kind/bug Categorizes issue or PR as related to a bug. label Apr 9, 2021
@jmcshane
Copy link
Contributor

jmcshane commented Apr 9, 2021

This is the same issue as #1026. I'll have a PR up soon to resolve for the v0.13.0 release

@jmcshane
Copy link
Contributor

jmcshane commented Apr 9, 2021

Thanks for this report @VeereshAradhya. I believe this is a regression in release v0.12.1. You can downgrade to v0.12.0 or take a look at #1037

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants