-
Notifications
You must be signed in to change notification settings - Fork 91
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
Comments
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? |
@tobio Yes, there's a plan to interface with the Kibana API. The provider should interact with all parts of the stack. /cc @shanisagiv1 |
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. |
@tobio I don't mind 10x'ing any estimate, so long we get it done.. |
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 tofalse
)Example1 :
if an Elasticsearch block is configured, the kibana block should automatically pick up credentials as they should be the same.
Example2 :
If only kibana is defined, it should require credentials to be mandatory
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.
The text was updated successfully, but these errors were encountered: