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

adding signal filters #54

Merged
merged 1 commit into from
Jul 24, 2018
Merged

adding signal filters #54

merged 1 commit into from
Jul 24, 2018

Conversation

magaldima
Copy link
Contributor

closes #26

@CLAassistant
Copy link

CLAassistant commented Jul 23, 2018

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

method: POST
filters:
time:
start: "2016-05-10T15:04:05Z07:00"
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this mean that the trigger will be fired only if the signal is fired between the start and stop time?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes

// DataFilter describes constraints and filters for event data
// Regular Expressions are purposefully not a feature as they are overkill for our uses here
// See Rob Pike's Post: https://commandcenter.blogspot.com/2011/08/regular-expressions-in-lexing-and.html
type DataFilter struct {
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you add an example for DataFilter as well?

Copy link
Contributor

Choose a reason for hiding this comment

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

Never mind.. Just saw it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

lemme know if I have enough examples

@@ -0,0 +1,316 @@
package controller
Copy link
Contributor

Choose a reason for hiding this comment

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

Great job on adding unit tests! :-)

shrinandj
shrinandj previously approved these changes Jul 24, 2018
Copy link
Contributor

@shrinandj shrinandj left a comment

Choose a reason for hiding this comment

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

Looks great!

@magaldima
Copy link
Contributor Author

magaldima commented Jul 24, 2018

These generated conflicts are annoying.. are these a feature of the

[[constraint]]
  name = "k8s.io/code-generator"
  branch = "release-1.10"

dependency?

Anyway, do you know if it matters how I resolve these conflicts?

Also side note, every time I now do make codegen I have to manually delete some fake Discovery code that you pointed out in #51 . Do you think we should raise an issue in the kubernetes repo with this?

Created #56 for this.

@magaldima
Copy link
Contributor Author

@shrinandj rebased on top of master, can you re-approve?

@magaldima magaldima merged commit 5124282 into master Jul 24, 2018
@magaldima magaldima deleted the add-signal-filters branch July 25, 2018 12:53
juliev0 pushed a commit to juliev0/argo-events that referenced this pull request Mar 29, 2022
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.

Add filters for signals
4 participants