suzuki-shunsuke / go-graylog

Graylog API client for Go and terraform provider for Graylog
https://github.com/terraform-provider-graylog/terraform-provider-graylog
MIT License
45 stars 11 forks source link

Support views #182

Open fcoelho opened 4 years ago

fcoelho commented 4 years ago

Views became part of the open source Graylog in 3.1

image

suzuki-shunsuke commented 4 years ago

WIP #183

Karreg commented 4 years ago

Hello,

This is also the only way now to handle dashboards. With Graylog 3.1+, the provider can't create dashboards anymore... Or to be more precise, they are created, but can't be reached through the GUI... :(

suzuki-shunsuke commented 4 years ago

@Karreg Please tell us the version of Graylog which you use. I confirmed that I can create a Dashboard with this provider and can access to the Dashboard though the web browser.

I'm using

https://github.com/suzuki-shunsuke/go-graylog/blob/a26bd268c99483896b456e972309aa5ed0d2c88c/examples/v0.12/dashboard.tf

image

Karreg commented 4 years ago

Sure.

I'm using

By using the provider, the dashboard is created, and can be seen through the API endpoint <graylog>/api/dashboards.

But it does not appear in the GUI. The GUI is using the dashboards by using the API endpoint <graylog>/api/views/dashboards that does not contain the dashboard created by the terraform provider.

Maybe the new API becomes mandatory with version 3.2? This would be a bad move from them to still keep the old API while it's not used anymore...

suzuki-shunsuke commented 4 years ago

Thank you for your information. I'll check in this weekend.

suzuki-shunsuke commented 4 years ago

I confirmed that the API /api/dashboards is treated as legacy on Graylog v3.2 as you said. Thank you for your information.

The data structure of Views API's request and response body is too complicated to implement it as usual. So I'm seeking a good way to support this.

Karreg commented 4 years ago

Thanks for the feedback. I'll try to work with content packs API to move on with my needs, and switch back to the provider someday in the future :)