Allow empty field name for supporting timeframe and keywords when validating rule during creation/update

[amsiglan]

Description

Allow empty field name for supporting timeframe and keywords when validating rule during creation/update

Check List

• Commits are signed per the DCO using --signoff

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.

[AWSHurneyt]

LGTM. Approving assuming tests pass.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8c636bd) 31.01% compared to head (5e568b0) 31.01%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #823   +/-   ##
=======================================
  Coverage   31.01%   31.01%           
=======================================
  Files         151      151           
  Lines        5101     5101           
  Branches      890      890           
=======================================
  Hits         1582     1582           
  Misses       3329     3329           
  Partials      190      190           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-823-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9fcb8452097a12bfada797076d8cbd9f1e4d9dae
# Push it to GitHub
git push --set-upstream origin backport/backport-823-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-823-to-2.x.

[opensearch-trigger-bot]

The backport to 2.9 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.9 2.9
# Navigate to the new working tree
cd .worktrees/backport-2.9
# Create a new branch
git switch --create backport/backport-823-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9fcb8452097a12bfada797076d8cbd9f1e4d9dae
# Push it to GitHub
git push --set-upstream origin backport/backport-823-to-2.9
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.9

Then, create a pull request where the base branch is 2.9 and the compare/head branch is backport/backport-823-to-2.9.

[opensearch-trigger-bot]

The backport to 2.10 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.10 2.10
# Navigate to the new working tree
cd .worktrees/backport-2.10
# Create a new branch
git switch --create backport/backport-823-to-2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9fcb8452097a12bfada797076d8cbd9f1e4d9dae
# Push it to GitHub
git push --set-upstream origin backport/backport-823-to-2.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.10

Then, create a pull request where the base branch is 2.10 and the compare/head branch is backport/backport-823-to-2.10.