Adding remote indices and multi index functionality

[amitgalitz]

Description

1. Adding the ability to fetch information on remote clusters and select which clusters we want to choose datasources from
2. Adds the ability to get information from remote indices such as the mapping
3. Add the ability to select more the one index/alias/index-pattern
4. Only resets the chosen model configuration if an index has been removed but not added

Issues Resolved

resolves #856
resolves #855

Check List

• New functionality includes testing.
  • All tests pass
• 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.

[kaituo]

If both newSelectedOptions and oldSelectedOptions are null or undefined, would it make more sense for isSelectedOptionIndexRemoved to return false instead of true, because if both are null or undefined, there is no change in the selection state — technically, no option was "removed." ?

[amitgalitz]

Originally if both were null it was okay for me to set it to true because then it would also make sense to reset the model configuration if we can't find any selected indices.
I think actually though we pretty much never hit the case where both are undefined so it wasn't making too much of an effect and it logically makes more sense to say indexRemoved is false in that case and if we got to this point we would have had an indexRemoved previously.
I tested it out and removing !(newSelectedOptins && oldSelectedOptions) and adding:

    if (_.isEmpty(oldSelectedOptions) && _.isEmpty(newSelectedOptions)) {
      return false;
    }

also works

[kaituo]

make sense

[kaituo]

cypress test is failing. Can you either fix it or make sure it passes locally?

[amitgalitz]

cypress test is failing. Can you either fix it or make sure it passes locally?

It does pass locally, I'm not sure why its failing here.

[kaituo]

Cypress test failed with a different reason now:

plugins/anomaly-detection-dashboard 03:56 4 3 1 - - │
│ s-plugin/vis_augmenter/view_anomaly │
│ _events_spec.js

[kaituo]

I think I fixed the timeout error during historical cypress tests in #859 and opensearch-project/opensearch-dashboards-functional-test#1537

Not sure about events_spec.js cypress failure above.

[jackiehanyang]

Does this Object.assign works fine on merging nested structure? Should we create a new map object instead of mutating the mappings variable directly?

[amitgalitz]

I was reading online that Object.assign is more efficient which can be important as we can have indices with very large mappings. I tested it on complicated nested structures

[jackiehanyang]

overall lgtm, just I see E2E CI is failing. Please look into that to make sure it won't be a RC build blocker

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

[opensearch-trigger-bot]

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

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