I saw there is a pull request (#9) that appears to support the InsightOps product (which seems to be the successor of Logentries).

What's the plan regarding the InsightOps support? Would make sense to have a separate provider (eg. insightops_log) or just adapt this one to handle both Logentries and InsightOps?

This issue was originally opened by @wdullaer as hashicorp/terraform#9280. It was migrated here as a result of the provider split. The original body of the issue is below.

Terraform Version

0.7.4

Affected Resource(s)

provider: logentries
resource: logentries_log

Terraform Configuration Files

resource "heroku_drain" "test_logentries" {
  app = "test-app-name"
  url = "https://heroku.logentries.com/v1/drain/${logentries_log.test_logs.token}"
}

# We'll create a new logset so we don't need to recover the uuid of the heroku one out of band
resource "logentries_logset" "test_logset" {
  name = "test-logset"
  location = "heroku"
}

resource "logentries_log" "test_logs" {
  logset_id = "${logentries_logset.test_logset.id}"
  name = "test-log"
  source = "syslog"
  type = "heroku"
}

Expected Behavior

It should refresh the state

The resources got created successfully, but it errors when trying to refresh the state afterwards

Actual Behavior

It errors our with

failed to retrieve default log type list: Unknown request list_logtypes_default.

The logentries API is not well documented, but it appears that this list default logtypes call is not supported.
I also explicitly specified the logtype in the config file, so I'm not sure why it is trying to list the default types.

Steps to Reproduce

1. terraform apply
2. terraform plan

Receiving the following error during Plan for a workspace that has previously worked:

* logentries_logset.logset: 1 error(s) occurred:

* logentries_logset.logset: logentries_logset.logset: Could not retrieve account info: {"reason":"Account v1 not found","response":"error"}

Hi,

I think logentries changed something and the provider is not working. I get "account not found".

Terraform Version

Terraform v0.11.5

• provider.aws v1.11.0
• provider.logentries v0.1.0
• provider.template v1.0.0

Terraform Configuration Files

# Configure the Logentries provider
provider "logentries" {
  account_key = "${var.logentries_account_key}"
}

# Create a log set
resource "logentries_logset" "testapp_logs" {
  name = "testpp-logs"
}

# Create a log and add it to the log set
resource "logentries_log" "testapp_log" {
  logset_id = "${logentries_logset.testapp_logs.id}"
  name      = "testapp-log"
  source    = "token"
}

output "testapp_le_token" {
  value = "${logentries_log.testapp_log.token}"
}

Debug Output

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  + logentries_log.testapp_log
      id:               <computed>
      logset_id:        "${logentries_logset.testapp_logs.id}"
      name:             "testapp-log"
      retention_period: "ACCOUNT_DEFAULT"
      source:           "token"
      token:            <computed>

  + logentries_logset.testapp_logs
      id:               <computed>
      location:         "nonlocation"
      name:             "testpp-logs"


Plan: 2 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

logentries_logset.testapp_logs: Creating...
  location: "" => "nonlocation"
  name:     "" => "testpp-logs"

Error: Error applying plan:

1 error(s) occurred:

* logentries_logset.testapp_logs: 1 error(s) occurred:

* logentries_logset.testapp_logs: failed to create log testpp-logs: The account with ID `5bXXXXXX-09f8-XXXX-XXXX-XXXXXXXXc68X' not found.

Thanks,

This Terraform provider is scheduled to be archived on September 27th, 2018. HashiCorp may archive providers when they have insufficient activity to maintain them at a level consistent with our open source guidelines and community expectations.

What does archiving mean?

1. The code repository and all commit, issue, and PR history will still be available.
2. Existing released binaries will remain available on the releases site and available to terraform init.
3. Documentation for the provider will remain on the Terraform website.
4. Issues and pull requests are not being monitored, merged, or added.
5. No new releases will be published.
6. Nightly acceptance tests may not be run.

If anyone from the community is willing to maintain this provider, please reach out to the Terraform Provider Development Program at [email protected].