-
Notifications
You must be signed in to change notification settings - Fork 746
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
Support for passing complete event payload from signal to trigger #94
Conversation
f0224d4
to
263831c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left some comments for some minor changes
controllers/sensor/signal-filter.go
Outdated
if int(currentT.Day()) < 10 { | ||
currentDay = "0" + currentDay | ||
} | ||
currentTStr := fmt.Sprintf("%d-%s-%s", currentT.Year(), currentMonth, currentDay) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this may be a cleaner solution: https://stackoverflow.com/questions/23428033/losing-0-for-single-digit-hours-with-golang-time-package
currentTStr := fmt.Sprintf("%d-%s-%d", currentT.Year(), currentMonth, currentT.Day()) | ||
currentDay := fmt.Sprintf("%d", int(currentT.Day())) | ||
if int(currentT.Day()) < 10 { | ||
currentDay = "0" + currentDay |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above.
controllers/sensor/validate.go
Outdated
@@ -84,7 +84,15 @@ func validateSignalFilter(filter v1alpha1.SignalFilter) error { | |||
|
|||
func validateSignalTimeFilter(tFilter *v1alpha1.TimeFilter) error { | |||
currentT := metav1.Time{Time: time.Now().UTC()} | |||
currentTStr := fmt.Sprintf("%d-%d-%d", currentT.Year(), int(currentT.Month()), currentT.Day()) | |||
currentMonth := fmt.Sprintf("%d", int(currentT.Month())) | |||
if int(currentT.Month()) < 10 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
This is a guide for help in utilizing artifacts within Argo Events. Sensors use artifacts for two purposes: | ||
1. Object notifications for use in `Artifact` signals. (currently S3 bucket notifications are only supported) | ||
2. A Resource Object store for use in `Resource` triggers | ||
This is a guide for help in utilizing artifacts within Argo Events. Sensors use artifacts for Resource Object store for use in `Resource` triggers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and this is no longer for object notifications because of the minio listenBucketNotifications
implementation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup
docs/index.md
Outdated
@@ -3,8 +3,8 @@ | |||
## Why Argo Events? | |||
- Containers. Designed from the ground-up as Kubernetes-native. | |||
- Extremely lightweight. All gateways, with exception of calendar based gateway, are event-driven, meaning there is no polling involved. | |||
- Configurable. Select gateways you want to support, deploy those to Kubernetes and configure them on the fly | |||
- Extensible. Write custom gateways that cater to your business use cases in any language of your choice | |||
- Configurable. Configure gateways at the runtime |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove "the"
examples/gateways/resource.yaml
Outdated
@@ -9,7 +9,7 @@ spec: | |||
deploySpec: | |||
containers: | |||
- name: "resource-events" | |||
image: "argoproj/resource-gateway" | |||
image: "metalgearsolid/resource-gateway" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this supposed to be this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops.. updated the image
the argo-ci build & test is failing.. should we be concerned? I think we have to update the default test logs:
|
c573229
to
849a534
Compare
fixed the build problem and all tests pass locally. Its weird that namespace_test is failing in Argo CI |
3990fff
to
fe3cea4
Compare
…er. Updated docs (argoproj#94)
No description provided.