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

Input Validation for Monitor Fields #1779

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

vikhy-aws
Copy link

@vikhy-aws vikhy-aws commented Jan 23, 2025

Description

This PR adds regex validations to monitor name, trigger name and destination id fields of a monitor. Validations are only added before creating/updating a monitor to ensure that functionality of the existing monitors do not break due to these new validation constraints. Includes tests for the same.

This PR depends on the changes in opensearch-project/common-utils#771

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

… a monitor. add tests to ensure that functionality of existing monitors do not break.

Signed-off-by: vikhy-aws <[email protected]>
throw IllegalArgumentException("Illegal trigger type, ${it.javaClass.name}, for bucket level monitor")
throw IllegalArgumentException("Illegal trigger type, ${it.javaClass.name}, for bucket level monitor.")
}
if (!isValidName(it.name)) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Discussed with @vikhy-aws offline that it would be helpful to add a validate function to the trigger interface to validate the various fields rather than adding each check here. Specific trigger types (e.g., bucket level trigger) can then override the interface's validate function as needed to accommodate their specific validation scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants