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

[Feature] Support Kibana connection in provider & in kibana resources #100

Closed
Kushmaro opened this issue Apr 25, 2022 · 4 comments
Closed
Assignees
Labels
enhancement New feature or request Kibana Kibana related APIs
Milestone

Comments

@Kushmaro
Copy link
Contributor

In order for us to be able to manage Kibana resources, the provider connection block should also support kibana.
the kibana connection block should also accept an insecure = true parameter, that accept untrusted certificates. (this parameter value defaults to false)

Example1 :

if an Elasticsearch block is configured, the kibana block should automatically pick up credentials as they should be the same.

provider "elasticstack" {
  elasticsearch {
    username  = "elastic"
    password  = "changeme"
    endpoints = ["http://localhost:9200"]
  }
  kibana {
    endpoints = ["https://my.kibana.url.com:<port>"]
    insecure = true
  }
}

Example2 :

If only kibana is defined, it should require credentials to be mandatory

provider "elasticstack" {
  kibana {
    username  = "elastic"
    password  = "changeme"
    endpoints = ["https://my.kibana.url.com:<port>"]
  }
}

Lastly, any kibana resource created in the provider should support the same sort of connection specification like the elasticsearch resources do, so that customers can create deployments using the Elastic Cloud terraform provider, and configure them on the fly.

@Kushmaro Kushmaro added the enhancement New feature or request label Apr 25, 2022
@Kushmaro Kushmaro added this to the 0.4.0 milestone Apr 25, 2022
@Kushmaro Kushmaro added the Kibana Kibana related APIs label Apr 25, 2022
@tobio
Copy link
Member

tobio commented Oct 17, 2022

Is there a plan around interfacing with the Kibana API? AFAIK Elastic doesn't provide a Go (or any other language) client for the Kibana API. If there's an expectation that we build that client as part of adding TF support for those resources then it's going to add significantly to the dev time on these tasks. Is there capacity within the Clients team to at least provide the scaffold for these clients?

@Kushmaro (@d-carmo for transparency)

@Kushmaro
Copy link
Contributor Author

@tobio Yes, there's a plan to interface with the Kibana API. The provider should interact with all parts of the stack.
The ResponseOps team have rules and alerts for TF on their roadmap.

/cc @shanisagiv1

@tobio
Copy link
Member

tobio commented Oct 17, 2022

Sure, but who's building the actual api client? If it's us then 10x any estimate for this task since we'd also have to build all the basics of an API client.

@Kushmaro
Copy link
Contributor Author

@tobio I don't mind 10x'ing any estimate, so long we get it done..
we can discuss the details of what's needed and which team's can help internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Kibana Kibana related APIs
Projects
None yet
Development

No branches or pull requests

4 participants