[2.x] Adding provision to invoke stop-replication from other plugins

[aggarwalShivani]

Description

Backport of #1391 on 2.x branch. Pls see the PR on main branch for complete background.
Mainly, the changes are ->

• StopIndexReplicationAction and StopIndexReplicationRequest are moved from the ccr project to common-utils. (Common-utils change PR)
• Added a new transport action, TransportInternalStopIndexReplicationAction - that can be used by other plugins like ism, to invoke stop-replication.

Related Issues

Stop replication feature in ism

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

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.

[aggarwalShivani]

Currently, CI checks are failing as required changes in common-utils PR are not yet merged.

[aggarwalShivani]

Hi @ankitkala

Looks like, unlike other plugins, the ccr plugin zipfiles do not get published anymore at this link -
https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/opensearch-cross-cluster-replication, even though i see build.sh has the publish task.

Can you pls guide here on what is missing?

As part of this feature, we want to install ccr-plugin during integTest stage in ism plugin. Pls see for reference. Pls guide on how this can be achieved.

[aggarwalShivani]

Hi @ankitkala

Looks like, unlike other plugins, the ccr plugin zipfiles do not get published anymore at this link - https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/opensearch-cross-cluster-replication, even though i see build.sh has the publish task.

Can you pls guide here on what is missing?

Hi @ankitkala
Any suggestions here?

[bowenlan-amzn]

LGTM!

[bowenlan-amzn]

Just to clarify, if user wants to use CCR in ISM in a security enabled cluster, they will still need the internal replication action allowed, right?

[aggarwalShivani]

Thats right !

For current ccr users, no change - they can continue to use roles like cross_cluster_replication_follower_full_access for all ccr operations.
For users who use ccr + ism, they'll additionally need permission for the internal replication action indices:internal/plugins/replication/index/stop