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

Handle empty namespace on trigger resources #224

Conversation

dtaniwaki
Copy link
Member

I set sensor's namespace as the default namespace of trigger resources, and added the tests.

I found OpenAPI spec is not updated when I executed make openapi-gen, so the PR also includes OpenAPI spec update for some other PRs.

Fixes #214

@dtaniwaki
Copy link
Member Author

I think we should verify codegen in CI to avoid unexpected diff in another PR.

@VaibhavPage
Copy link
Contributor

Agreed.

VaibhavPage
VaibhavPage previously approved these changes Mar 12, 2019
@VaibhavPage
Copy link
Contributor

Getting

Failures:

  • /home/travis/gopath/src/github.com/argoproj/argo-events/sensors/trigger_test.go
    Line 264:
    Expected: nil
    Actual: 'pods "my-pod" not found'
  • /home/travis/gopath/src/github.com/argoproj/argo-events/sensors/trigger_test.go
    Line 277:
    Expected: nil
    Actual: 'pods "my-pod" not found'

@VaibhavPage VaibhavPage merged commit ec51559 into argoproj:master Mar 13, 2019
@dtaniwaki dtaniwaki deleted the handle-empty-namespace-on-trigger-resources branch March 13, 2019 11:49
juliev0 pushed a commit to juliev0/argo-events that referenced this pull request Mar 29, 2022
* Set sensor namespace on trigger resources by default

* Update OpenAPI gen

* Update Gopkg.lock

* Fix tests

* Make condition easier to read
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants