-
Notifications
You must be signed in to change notification settings - Fork 805
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
Add ES support for ListAllWorkflowExecutions #6157
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@@ -445,7 +444,38 @@ func (v *esVisibilityStore) ListWorkflowExecutions( | |||
} | |||
|
|||
func (v *esVisibilityStore) ListAllWorkflowExecutions(ctx context.Context, request *p.InternalListAllWorkflowExecutionsByTypeRequest) (*p.InternalListWorkflowExecutionsResponse, error) { | |||
return nil, p.ErrVisibilityOperationNotSupported | |||
isRecordValid := func(rec *p.InternalVisibilityWorkflowExecutionInfo) bool { | |||
return !request.EarliestTime.After(rec.StartTime) && !rec.StartTime.After(request.LatestTime) |
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.
I guess this should also be covered with tests
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.
LGTM.
Side note: do we want to onboard to using query builders, like https://github.com/defensestation/osquery or https://github.com/aquasecurity/esquery
What changed?
ES support for ListAllWorkflowExecutions
Why?
ES is still used in many clusters and we need support for ListAllWorkflowExecutions
How did you test it?
unit tests
Potential risks
Release notes
Documentation Changes