-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Rely on Datadog API to validate the query #2771
Conversation
/run-e2e datadog* |
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!
Thanks for this improvement ❤️
Could you update the changelog?
8b2cdc3
to
904f380
Compare
@JorTurFer thanks for the review! Updated the changelog |
/run-e2e datadog* |
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!
Thanks for your awesome contributions! ❤️
@arapulido |
Signed-off-by: Ara Pulido <ara.pulido@datadoghq.com>
Signed-off-by: Ara Pulido <ara.pulido@datadoghq.com>
Signed-off-by: Ara Pulido <ara.pulido@datadoghq.com>
904f380
to
8bd04da
Compare
done! |
Signed-off-by: Ram Cohen <ram.cohen@gmail.com>
Instead of trying to validate all potential valid queries ahead of creating the scaledobject, rely on the Datadog API to do so and return the error returned by the API if that happens. Also, rely on the Datadog API to apply the default rollup time frame if one is not specified in the query.
This way, if there are any addition to the query language down the line, we won't need to change the scaler code, while simplifying it.
Checklist
Fixes #2761