Adding max http response string length as a setting, and capping http…

[toepkerd]

Adding max http response string length as a setting, and capping http response string based on that setting

Description

This is a 2.x version of the following change merged to main/3.0: #861. 2.x did not have all the necessary libraries that this change needed, so they were reimplemented for the purposes of working on older versions.

Issues Resolved

Please refer to #861

Check List

• [Y] 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]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.85%. Comparing base (35b9e19) to head (0e53be1).
Report is 2 commits behind head on 2.x.

❗ Current head 0e53be1 differs from pull request most recent head 0b764ed. Consider uploading reports for the commit 0b764ed to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##                2.x     #876   +/-   ##
=========================================
  Coverage     66.85%   66.85%           
  Complexity      263      263           
=========================================
  Files            39       39           
  Lines          1738     1738           
  Branches        165      165           
=========================================
  Hits           1162     1162           
  Misses          453      453           
  Partials        123      123           

Flag	Coverage Δ
opensearch-notifications	66.85% <ø> (ø)

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

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

[Hailong-am]

LGTM, thanks

[Hailong-am]

can we move this truncate logic to a util class like EntityUtils?

[toepkerd]

If we do let's keep it as a backlog item

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

[opensearch-trigger-bot]

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

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