-
Notifications
You must be signed in to change notification settings - Fork 60
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] Index patterns resource type #56
Comments
[Untriage]
@arichtman-srt can you take a look and contribute this index_pattern setting to the provider? |
From code side I did found the |
@prudhvigodithi
|
Just a few things based on the opensearch_dashboard_object approach:
otherwise terraform wants to change this at every plan/apply - I guess it's related to the opensearch version. => @rblcoder : Because of those 3 points above, I think there's a case for actually creating a dedicated terraform resource. do you think it's worth re-opening ? |
@PhilippReinke would it be possible for you to look into the query above regarding index patterns? |
A working example of index pattern |
Hi :) here is an example index-pattern that is based on the comment @rblcoder linked but without tenant. By default you've got an index of the form "security-auditlog-*" and with the latest OpenSearch version you can create an index-pattern with
where I have used the sample docker-compose.yml to test it. Regarding your bullet points
The provider stores the dashboard objects in the .kibana index. So, you can fetch the object under DevTools with
Regarding a dedicated terraform resource I think that would be really nice feature. However, one would have to deal with different OpenSearch versions and the dashboards objects are not well documented. Actually, there should be a terraform resource for every dashboard object. The current For Kibana there is a Saved Objects API that even states
In the future there might be a documented Saved Objects API in OpenSearch. The provider could communicate with the OpenSearch Dashboard API and not the OpenSearch API anymore. |
Thank you @PhilippReinke |
Thank you @rblcoder and @PhilippReinke - that was really well explained and interesting |
@jgournet Glad it was helpful |
Thanks @PhilippReinke @rblcoder, I agree on the following points.
To begin with we should move to dashboard But looks like |
Here is an open issue for creating index_pattern with API opensearch-project/OpenSearch-Dashboards#910, but there is a comment here that says as possible with |
It's a question of how tightly we want to model the API. We can work with the generic dashboards object for now so it's no longer a blocking issue, just less ergonomic :). Thanks to all involved for your time too! |
Is your feature request related to a problem?
I'm unable to create all the necessary objects by way of Terraform.
Index Patterns, which I think you need for data streams, are not present in the provider.
Though it might be a Kibana concept?
What solution would you like?
A resource type
opensearch_index_pattern
that operates about the same as everything else in the provider.What alternatives have you considered?
Combination of
local_file
withjsonencode
andnull
resource oflocal_script
to manuallycurl
the API.Do you have any additional context?
https://www.elastic.co/guide/en/kibana/7.17/index-patterns.html
The text was updated successfully, but these errors were encountered: