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

fix #4994 use trigger's namespace only when subscriber's namespace is nil #4995

Merged
merged 1 commit into from
Mar 5, 2021

Conversation

zhaojizhuang
Copy link
Member

@zhaojizhuang zhaojizhuang commented Mar 1, 2021

Fixes #4994 #4628

Proposed Changes

Release Note

Allow Trigger users to set another namespace's Subscriber, And when Subscriber's namespace not been set, it will be set to  Trigger's namespace 

Docs

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Mar 1, 2021
@knative-prow-robot knative-prow-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 1, 2021
@zhaojizhuang
Copy link
Member Author

/assign @pierDipi

@zhaojizhuang
Copy link
Member Author

/assign @slinkydeveloper

@codecov
Copy link

codecov bot commented Mar 1, 2021

Codecov Report

Merging #4995 (31399c5) into master (d6d48a7) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4995      +/-   ##
==========================================
- Coverage   82.63%   82.60%   -0.03%     
==========================================
  Files         294      294              
  Lines        8401     8401              
==========================================
- Hits         6942     6940       -2     
- Misses       1062     1063       +1     
- Partials      397      398       +1     
Impacted Files Coverage Δ
pkg/reconciler/mtbroker/trigger/trigger.go 80.00% <0.00%> (-1.54%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d6d48a7...a38e9e9. Read the comment docs.

@zhaojizhuang
Copy link
Member Author

/test pull-knative-eventing-integration-tests

@slinkydeveloper
Copy link
Contributor

/lgtm
/approve

/hold for @vaikas review

@knative-prow-robot knative-prow-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 1, 2021
@zhaojizhuang
Copy link
Member Author

cc @vaikas #4994 (comment)

@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 3, 2021
@zhaojizhuang
Copy link
Member Author

/ok-to-test

@knative-prow-robot knative-prow-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Mar 3, 2021
@zhaojizhuang
Copy link
Member Author

cc @vaikas

@zhaojizhuang
Copy link
Member Author

/test pull-knative-eventing-unit-tests

@zhaojizhuang
Copy link
Member Author

/retest

@zhaojizhuang
Copy link
Member Author

@pierDipi @mattmoor The UT robot didn't pull the right code,and fun failed
image

@pierDipi
Copy link
Member

pierDipi commented Mar 3, 2021

hmm, that's weird
/retest

@pierDipi
Copy link
Member

pierDipi commented Mar 3, 2021

If you rebase you will see the error locally as well.

@pierDipi
Copy link
Member

pierDipi commented Mar 3, 2021

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2021
@zhaojizhuang
Copy link
Member Author

If you rebase you will see the error locally as well.

@pierDipi but it run successfully locally

@zhaojizhuang
Copy link
Member Author

/retest

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2021
@pierDipi
Copy link
Member

pierDipi commented Mar 4, 2021

I did it yesterday, did you update your master branch?

@zhaojizhuang
Copy link
Member Author

zhaojizhuang commented Mar 4, 2021

I did it yesterday, did you update your master branch?

@pierDipi yeah, I rebase it to run UT,but it failed again. can anyone fix the Robot?

@pierDipi
Copy link
Member

pierDipi commented Mar 4, 2021

zhaojizhuang#1

@zhaojizhuang
Copy link
Member Author

/retest

@knative-metrics-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-knative-eventing-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/reconciler/mtbroker/trigger/trigger.go 87.0% 86.1% -0.9

Copy link
Member

@pierDipi pierDipi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fixes #4628 too.

Can you add a release note? The example is in https://raw.githubusercontent.com/knative/eventing/master/.github/pull-request-template.md

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2021
@zhaojizhuang
Copy link
Member Author

This fixes #4628 too.

Can you add a release note? The example is in https://raw.githubusercontent.com/knative/eventing/master/.github/pull-request-template.md

/lgtm

yeah, happy to add a release note

@vaikas
Copy link
Contributor

vaikas commented Mar 4, 2021

Thanks!
/lgtm
/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierDipi, slinkydeveloper, vaikas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [pierDipi,slinkydeveloper,vaikas]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vaikas
Copy link
Contributor

vaikas commented Mar 4, 2021

/unhold

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2021
@zhaojizhuang
Copy link
Member Author

/test pull-knative-eventing-unit-tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

subscriber's NameSpace do not work in Trigger
6 participants