Release notes for 2.3.0

[mengweieric]

Signed-off-by: Eric Wei menwe@amazon.com

Description

Release notes for 2.3.0.

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• 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.

[codecov-commenter]

Codecov Report

Merging #459 (b8ac313) into main (c947f8d) will increase coverage by 2.58%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #459      +/-   ##
============================================
+ Coverage     74.27%   76.85%   +2.58%     
============================================
  Files            94       30      -64     
  Lines          3984     1923    -2061     
  Branches        641      412     -229     
============================================
- Hits           2959     1478    -1481     
+ Misses          891      442     -449     
+ Partials        134        3     -131     

Flag	Coverage Δ
dashboards-reports	76.85% <ø> (ø)
reports-scheduler	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...tsscheduler/action/DeleteReportDefinitionAction.kt
...opensearch/reportsscheduler/model/SearchResults.kt
...rch/reportsscheduler/security/UserAccessManager.kt
...nsearch/reportsscheduler/model/ReportDefinition.kt
...uler/model/ReportDefinitionDetailsSearchResults.kt
...g/opensearch/reportsscheduler/metrics/Metrics.java
...scheduler/resthandler/OnDemandReportRestHandler.kt
...tsscheduler/scheduler/ReportDefinitionJobParser.kt
...portsscheduler/model/ReportDefinitionDetailsDoc.kt
...rtsscheduler/model/GetAllReportInstancesRequest.kt
... and 54 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[eugenesk24]

Ships ahoy!

[opensearch-trigger-bot]

The backport to 2.x failed:

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

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-459-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b0c564338323056d33fddf30e70a5b0e59b69c6a
# Push it to GitHub
git push --set-upstream origin backport/backport-459-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-459-to-2.x.

[opensearch-trigger-bot]

The backport to 2.3 failed:

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

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.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-459-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b0c564338323056d33fddf30e70a5b0e59b69c6a
# Push it to GitHub
git push --set-upstream origin backport/backport-459-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3

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

[opensearch-trigger-bot]

The backport to 2.3 failed:

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

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.3 2.3
# Navigate to the new working tree
cd .worktrees/backport-2.3
# Create a new branch
git switch --create backport/backport-459-to-2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b0c564338323056d33fddf30e70a5b0e59b69c6a
# Push it to GitHub
git push --set-upstream origin backport/backport-459-to-2.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.3

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

[opensearch-trigger-bot]

The backport to 2.x failed:

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

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-459-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b0c564338323056d33fddf30e70a5b0e59b69c6a
# Push it to GitHub
git push --set-upstream origin backport/backport-459-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-459-to-2.x.