elastic / elastic/terraform-provider-elasticstack

Index and Lifecycle policy conflict

Open
#94 11 comments 1 reaction 0 assignees View on GitHub
bug enhancement needs-human triaged
Dominant language
Go
Stars
209
Forks
150
Avg merge
22h 58m
Merged PRs (30d)
172

Description

Something I noticed is that when you're creating a lifecyle policy with a delete step and you create the initial index using terraform, the lifecycle will delete the initial index. When you redeploy the terraform template the since-deleted index will be recreated, which is the expected behavior. The problem however, is that the index alias will be applied to the newly recreated index causing a conflict with the lifecycle policy on the next rollover.

Any advice on how to get around this?

Contributor guide

No contributing guide indexed for this repository

Research direction

No file or test is named. Start by reviewing the Terraform template and reproducing the interaction between the delete lifecycle step, the recreated initial index, and its alias in Elasticsearch. Done means the conflicting rollover behavior is prevented or clearly documented with a verified configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, go, terraform
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.