Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix alias exists check in findings index creation #622

Merged
merged 1 commit into from
Oct 25, 2022

Conversation

eirsep
Copy link
Member

@eirsep eirsep commented Oct 25, 2022

Signed-off-by: Surya Sashank Nistala snistala@amazon.com

@eirsep eirsep requested a review from a team October 25, 2022 02:59
Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>
@@ -326,7 +326,7 @@ class AlertIndices(
}
val findingsIndex = dataSources.findingsIndex
val findingsIndexPattern = dataSources.findingsIndexPattern ?: FINDING_HISTORY_INDEX_PATTERN
if (!clusterService.state().routingTable().hasIndex(findingsIndex)) {
if (!clusterService.state().metadata().hasAlias(findingsIndexPattern)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it be either of the index pattern or index name present?

@eirsep eirsep merged commit ce79ffd into opensearch-project:main Oct 25, 2022
opensearch-trigger-bot bot pushed a commit that referenced this pull request Oct 25, 2022
Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>

Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>
(cherry picked from commit ce79ffd)
sbcd90 pushed a commit that referenced this pull request Oct 25, 2022
Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>
sbcd90 pushed a commit to sbcd90/alerting that referenced this pull request Nov 2, 2022
sbcd90 pushed a commit that referenced this pull request Nov 2, 2022
Signed-off-by: Surya Sashank Nistala <snistala@amazon.com>
@opensearch-trigger-bot
Copy link
Contributor

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants