-
Notifications
You must be signed in to change notification settings - Fork 12
error after terraform configuration #127
Comments
Hello.
And it is the Graylog's problem. |
terraform simply calls Graylog API. |
for reproduce:
terraform code, there is complete configuration, i will investigate if some source is problem. |
Hi, https://github.com/suzuki-shunsuke/go-graylog/blob/master/terraform/docs/stream.md |
Hi, resource "graylog_stream" "stream01" { |
Thank you for your feedback! Although I don't know whether it is also correct on Terraform v0.12, https://www.terraform.io/docs/configuration-0-11/variables.html#booleans
|
Thank you for your feedback! POST /streams request body {
"title": "test",
"index_set_id": "5cdf8c8ed497d2000f0a3bc9"
} response response code: 201 response body {
"stream_id": "5d2289bcd497d2000f72109d"
} created stream {
"id": "5d2289bcd497d2000f72109d",
"creator_user_id": "admin",
"outputs": [],
"matching_type": "AND",
"description": null,
"created_at": "2019-07-08T00:09:32.347Z",
"disabled": true,
"rules": [],
"alert_conditions": [],
"alert_receivers": {
"emails": [],
"users": []
},
"title": "test",
"content_pack": null,
"remove_matches_from_default_stream": false,
"index_set_id": "5cdf8c8ed497d2000f0a3bc9",
"is_default": false
} The description of the created stream is |
I add the parameter |
Hi Suzuki, for streams, this configuration is for me correct: to add description was not solution, but to add disabled = "false" and is_default = "false" in "" was solution. The same error i have by stream rule :(, others resources are ok. |
Hi, type = 1 for "must match exactly"
|
remove boolean from examples because the treat of boolean in the terraform configuration is ambiguous and it is out of scope of this provider's document. #127 (comment)
I have fixed the document. |
@suzuki-shunsuke according to the official API we don't have 'ID - 0'
maybe we should use "name" instead of 'id' ? For me it's a little bit strange that API allows us creating 'broken' resources. I have made the issue in the graylog bugtracker |
hi, please advice.
I have these errors after application terraform configuration and restart graylog docker container. With manual configuration after restart graylog is ok.
Please, did you test terraform code to docker imlementation? After restart is it working?
Thanks
The text was updated successfully, but these errors were encountered: