[Bugfix] Add already mapped log index fields to list of mapping options

[amsiglan]

Description

When we have automatically mapped fields, if the user removes the mapped log index field, then it is not added back to the list of available options and user cannot add the same field back without a workaround.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7837a99) 31.03% compared to head (c370f3d) 31.03%.
Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #845   +/-   ##
=======================================
  Coverage   31.03%   31.03%           
=======================================
  Files         151      151           
  Lines        5111     5113    +2     
  Branches      948      895   -53     
=======================================
+ Hits         1586     1587    +1     
- Misses       3335     3336    +1     
  Partials      190      190           

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

[eirsep]

plz udpate the PR description and use the exact terminologies like Mapped Fields and Available Fields

If i understood this.. this pr seems to move a field from Mapped field to Available fields if the user removes the automatical mapping

is that right??

[amsiglan]

plz udpate the PR description and use the exact terminologies like Mapped Fields and Available Fields

If i understood this.. this pr seems to move a field from Mapped field to Available fields if the user removes the automatical mapping

is that right??

No, all this change does is make sure if the user deselects the provided automatic mapping, they can select that option again. Currently, we end up removing that option altogether

[opensearch-trigger-bot]

The backport to 2.9 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security-analytics-dashboards-plugin/backport-2.9 2.9
# Navigate to the new working tree
pushd ../.worktrees/security-analytics-dashboards-plugin/backport-2.9
# Create a new branch
git switch --create backport-845-to-2.9
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9ac83da0ccb80ae5ecb133e41490fa5d69660c0
# Push it to GitHub
git push --set-upstream origin backport-845-to-2.9
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-analytics-dashboards-plugin/backport-2.9

Then, create a pull request where the base branch is 2.9 and the compare/head branch is backport-845-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:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security-analytics-dashboards-plugin/backport-2.10 2.10
# Navigate to the new working tree
pushd ../.worktrees/security-analytics-dashboards-plugin/backport-2.10
# Create a new branch
git switch --create backport-845-to-2.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9ac83da0ccb80ae5ecb133e41490fa5d69660c0
# Push it to GitHub
git push --set-upstream origin backport-845-to-2.10
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-analytics-dashboards-plugin/backport-2.10

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

[opensearch-trigger-bot]

The backport to 2.11 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security-analytics-dashboards-plugin/backport-2.11 2.11
# Navigate to the new working tree
pushd ../.worktrees/security-analytics-dashboards-plugin/backport-2.11
# Create a new branch
git switch --create backport-845-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9ac83da0ccb80ae5ecb133e41490fa5d69660c0
# Push it to GitHub
git push --set-upstream origin backport-845-to-2.11
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-analytics-dashboards-plugin/backport-2.11

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

[opensearch-trigger-bot]

The backport to 2.12 failed:

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

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/security-analytics-dashboards-plugin/backport-2.12 2.12
# Navigate to the new working tree
pushd ../.worktrees/security-analytics-dashboards-plugin/backport-2.12
# Create a new branch
git switch --create backport-845-to-2.12
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e9ac83da0ccb80ae5ecb133e41490fa5d69660c0
# Push it to GitHub
git push --set-upstream origin backport-845-to-2.12
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/security-analytics-dashboards-plugin/backport-2.12

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