terraform-provider-sumologic
terraform-provider-sumologic copied to clipboard
SumoLogic
Terraform provider for Sumo Logic
The REST API documentation indicates that the list of identifiers projected from the parse expression configured in the `field_extraction_rule` resource. The json data for `fieldNames` will contain an array of...
The field `value_type` within the `field` schema would benefit greatly with additional information. This is an important field to determine what kind of log mapping is needed. Documentation here is...
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.35.0 to 0.38.0. Commits e1fcd82 html: properly handle trailing solidus in unquoted attribute value in foreign... ebed060 internal/http3: fix build of tests with GOEXPERIMENT=nosynctest 1f1fa29 publicsuffix: regenerate...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.33.0 to 0.35.0. Commits 7292932 ssh: limit the size of the internal packet queue while waiting for KEX f66f74b acme/autocert: check host policy before probing the cache...
- [Sumo Logic Docu](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/Amazon-Web-Services/AWS-S3-Source#Scan+Interval+in+step+11) suggests to set `Scan Interval` to `Automatic` when used along with `SNS Subscription Endpoint` but `scan_interval` from `sumologic_s3_source` resource is of type `int` — how to...
Hey! Thanks for the great provider, having some issues with the Cloudtrail piece though. Example configuration: ``` resource "sumologic_cloudtrail_source" "terraform_cloudtrail_source" { name = "Amazon Cloudtrail" description = "Cloudtrail logs from...
Due to different configuraton of c2c sources, where the source name is located in the `config` block, the current import by name methods do not work.
The resource `sumologic_cloudfront_source` currently haven't the options to configure "Log file discovery" that connects the resource with an SNS topic in the aws side.
When user provides incorrect credentials he gets something like ``` Error: Error 401 User could not be found. HTTP ERROR 401 User could not be found. URI:/api/v1/fields STATUS:401 MESSAGE:User could...
When user uses base URL like `https://api.sumologic.com/api/v1/` instead of `https://api.sumologic.com/api/` then provider instead of handling that prints the following ``` Error: {"id":"O6SOJ-9BDH3-YQG04","errors":[{"code":"unauthorized","message":"Credential could not be verified."}]} ``` It would be...