elastic / elastic/terraform-provider-elasticstack

[Feature] Add support for kibana space advanced settings

Open
#709 2 comments 15 reactions 0 assignees View on GitHub
enhancement needs-research no-kibana-support triaged
Dominant language
Go
Stars
209
Forks
150
Avg merge
23h 11m
Merged PRs (30d)
169

Description

**Describe the resource you would like to have implemented.**
more user-friendly advanced settings for Kibana space

**Describe the solution you'd like**
new option with advanced_settings under elasticstack_kibana_space or new resource

**Describe alternatives you've considered**
I tried to use elasticstack_kibana_import_saved_objects. But there is a problem with upgrades. You have to manage a lot of fields like `typeMigrationVersion`, `coreMigrationVersion`, `buildNum`, ...

Currently, I created my provider which uses `/s/%s/internal/kibana/settings`

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the implementation of elasticstack_kibana_space and the existing elasticstack_kibana_import_saved_objects flow, then inspect the /s/%s/internal/kibana/settings endpoint behavior. Define whether advanced_settings belongs on the space resource or a new resource, and verify upgrades do not require managing fields such as typeMigrationVersion, coreMigrationVersion, or buildNum.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.