erikvanbrakel / terraform-provider-sumologic

This project is done. It has been integrated into https://github.com/SumoLogic/sumologic-terraform-provider

terraform-provider-sumologic

Terraform provider for https://sumologic.com

Building the provider

In this section you will learn how to build and run terraform-provider-sumologic locally. Please follow the steps below:

Requirements

• Terraform 0.9.x
• Go 1.8 (to build the provider plugin)
• Sumologic Must have an account to be able to get access id and key.

Setting your environment

Create the couple environment variables below:

$GOROOT = $HOME/go

$GOPATH = $GOROOT/bin

The GOPATH can be set wherever you want but please read this topic to understand how they work.

Clone repository to: $GOPATH/src/github.com/erikvanbrakel/terraform-provider-sumologic Terraform provider for https://sumologic.com

Installation

Download the binary for your platform and architecture from the releases page. Unpack the zip, and place the terraform-provider-sumologic binary in the same directory as terraform binary or add a .terraformrc file with the provider stanza:

providers {
  sumologic = "/PATH/TO/MODULE/ARCH/terraform-provider-sumologic"
}

Usage

See the documentation.

terraform-provider-sumologic's Issues

Update releases

0.2.3 release happened a while ago and some good stuff was added since then.

Could you create a new release? Thanks

Publish to Module Registry

Add provider to Terraform Module Registry

https://www.hashicorp.com/blog/hashicorp-terraform-module-registry/

Allow updating of collector resource

#21 implements this.

How do you use this?

Can you show some examples of using this provider with resources?

The provider is not saving its state

Hi! @erikvanbrakel

I've been using your provider for a while now and everything is working really good! 😃
I just wanna ask you if you're planning to add the function that saves the state of Sumologic.
For example, I just created a new Collector with a Polling Source and they're created successfully. However, any changes made in my terraform code, in sumologic resources, are not saved in the terraform.tfstate. So, whenever I run terraform plan it says that there are no changes in my code.

Another question, are you also planning to make a pull request to terraform to add this provider in a near future?

Thank you again!

Investigate options for sumologic API access

External or internal?
https://github.com/BSick7/sumologic-sdk-go/blob/master/api/sources.go

Support for DE collector

It seems that this region isn't supported.

Set up CI builds

Improve error handling

When something goes wrong, the current error messages don't really point you in any direction. In general, it just complains about JSON format or something....

exits without any error

The plan goes without an issue , but when trying to apply it just dies without any exception

{code}
Error: Error applying plan:

1 error(s) occurred:

• module.cluster_bootstrap.sumologic_collector.collector: 1 error(s) occurred:

• sumologic_collector.collector:

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
{code}

config is pretty standard as per the readme

Thanks
NIro

permission denied / file does not exist

Hi!
Sorry if this is considered a silly question since I'm a bit new to Terraform, but I've been cracking my head with this for a while so...
I followed your tutorial step by step, word by word and I tried in both Windows and Ubuntu.
In both cases when I try to run "terraform plan" I'm always getting this error message:
Ubuntu: provider.sumologic: fork/exec /github/terraform/terraform-provider-sumologic: permission denied
(+ I tried moving the .terraformrc file to terraform's folder and my project's folder)
Windows: provider.sumologic: exec: "C:\\HashiCorp\\Terraform\\terraform-provider-sumologic": file does not exist
In Ubuntu I've granted 777 permission to the folder & files and still same
My code is basically one terraform file as you see below:
`provider "aws" {
access_key = {my-access-key}
secret_key = {my secret key}
region = "us-west-2"
}

resource "aws_instance" "sumologic_terraform" {
ami = "ami-db6bf3bb"
instance_type = "t2.micro"
}

provider "sumologic" {
access_id = {my-access-id}
access_key = {my-access-key}
environment = "us-west-2"
}

resource "sumologic_collector" "collector" {
name = "redhat_collector"
description = "redhat generated by terraform with sumo"
category = "collector-container"
}`
Is there any other documentation that I should follow? I read this https://www.terraform.io/docs/plugins/basics.html but it didn't work as well...
If I got it wrong, really sorry about that, otherwise can you update your documentation with more details?
Thank you!

Add TimeZone attribute to collector

To get feature parity with the sumologic web UI.

problem with the `linux-amd64` binary

While trying to use the linux-amd64 binary for the 0.3.0 release here

I get the following error when trying to execute the binary:

/tmp # ls -l
total 21056
-rwxr-xr-x    1 root     root      16859366 Apr  6 20:59 terraform-provider-sumologic
-rw-r--r--    1 root     root       4695025 Apr  6 20:59 terraform-provider-sumologic.zip
/tmp # ./terraform-provider-sumologic
sh: ./terraform-provider-sumologic: not found

This inside an alpine:3.7 docker container.

Add more attributes to sources

see: https://help.sumologic.com/Send_Data/Sources/03Use_JSON_to_Configure_Sources

API rate limit for this user has been exceeded.

There needs to be a built in workaround for API rate limits, maybe adding a max_retries to the provider like the AWS provider offers, https://www.terraform.io/docs/providers/aws/#max_retries

Add polling source

Description

In order to support:

• AWS S3 Source
• AWS Elastic Load Balancing Source
• AWS CloudFront Source
• AWS S3 Audit Source

Suggested syntax:

resource "sumologic_collector" "AWS" {
    name = "AWS"
}

resource "sumologic_polling_source" "s3_audit" {
    collector_id = "${sumologic_collector.AWS.id}"
    name = "Amazon S3 Audit"
    content_type = "AwsS3AuditBucket"
    category = "aws/s3audit"
    scan_interval = 1
    paused = false

    authentication {
        access_key = "AKIAIOSFODNN7EXAMPLE"
        secret_key = "******"
    }

    path {
        bucket_name = "Bucket1"
        path_expression = "*"
    }
}

Issue refreshing state when deleting sumologic module

Hey there, I was experimenting with this provider inside of a module and ran into an issue when trying to remove the module I had instantiated. The error was not very clear:

Error refreshing state: 1 error(s) occurred:

* module.sumologic.sumologic_collector.cloudformation: sumologic_collector.cloudformation:

The module itself is quite simple:

main.tf

provider "sumologic" {
  environment = "${var.sumologic_environment}"
}

resource "sumologic_collector" "cloudformation" {
  name        = "${var.environment}-cloudformation"
  description = "Cloudformation logs for ${var.environment}"
}

resource "sumologic_http_source" "cloudformation" {
  name         = "HTTP"
  category     = "aws/cloudformation"
  collector_id = "${sumologic_collector.cloudformation.id}"

  # SumoLogic lambda batches messages into a single request
  messagePerRequest = "false"
}

outputs.tf

output "cloudformation_http_url" {
  description = "URL for the sumologic cloudformation http endpoint."

  value = "${sumologic_http_source.cloudformation.url}"
}

variables.tf

variable "environment" {
  description = "The environment name"
}

variable "sumologic_environment" {
  description = "The sumologic API endpoint to use. Default is us2."

  default = "us2"
}

I was eventually able to clean it up by removing the two resources defined inside the module from the module, plan + apply, and then remove the module instantiation. Any idea if there's an issue with the provider or possibly how I was using it?

Make http source updatable

Currently any change will force a rebuild.