When a provider is partially defined as the following example:

provider "lacewoek" {
	account    = "tech-ally"
	api_key    = "MYKEY_123abc"
}

And we run terraform apply, the provider will ask for the API Secret but it won't accept it:

$ terraform apply
provider.lacework.techally.api_secret
  Lacework API access secret

  Enter a value: foo


Error: Missing required attribute

  on <input-prompt> line 1:
  (source code not available)

The attribute "account" is required, but no definition was found.


Error: Missing required attribute

  on <input-prompt> line 1:
  (source code not available)

The attribute "api_key" is required, but no definition was found.

Terraform Provider Lacework docs should provide links to https://github.com/lacework/terraform-provisioning to help customers that want to manage both Lacework as well as their cloud provider.

The Lacework provider should be able to use the configuration file offered by the
Lacework CLI to load the required settings for its proper operation.

User Story

As a Lacework user that wants to integrate with Jira via Terraform,
I would like to have support for custom templates in my JIRA resources,
So I can populate values in new Jira issues created by Lacework.

Description

We need to add a new parameter to the Schema of the two Terraform
resources to create Jira integrations:

• lacework_alert_channel_jira_server
• lacework_alert_channel_jira_cloud

This parameter could be named custom_template.

First of all, thank you for all of the work on this Terraform provider!

Ideally, I'd like to create all Lacework integrations via Terraform. This is possible today for Google Cloud Platform compliance and audit trail integrations, but not for Google Container Registry. Here is the Lacework guide for setting up the GCR integration manually.

I imagine this resource would look similar to the lacework_integration_gcp_cfg resource.

As a Lacework customer and a Terraform user,
I want to use the Lacework Terraform Provider to configure Jira Alert Channel integrations in my Lacework account,
So I can configure and maintain multiple alerts as code.

Integration Type: JIRA

Jira Cloud Integration

provider "lacework" { }

resource "lacework_alert_channel_jira_cloud" "default" {
  name               = "default"
  jira_url           = "mycompany.atlassian.net"
  project_key        = "EXAMPLE"
  username           = "me"
  api_token          = "my-api-token"
  issue_type         = "Bug"
  group_issues_by    = "Events"
  min_alert_severity = 5
}

Jira Server Integration

provider "lacework" { }

resource "lacework_alert_channel_jira_server" "default" {
  name               = "default"
  jira_url           = "mycompany.atlassian.net"
  project_key        = "EXAMPLE"
  username           = "me"
  passwork           = "my-password"
  issue_type         = "Bug"
  group_issues_by    = "Resources"
  min_alert_severity = 1
}

JIRA: ALLY-159

When you run terraform apply after creating the resource, we are trying to update the
private_key when it is sensitive and will always be different. We should avoid updating the
resource:

 # module.gcp_project_audit_log.lacework_integration_gcp_at.default will be updated in-place
  ~ resource "lacework_integration_gcp_at" "default" {
        created_or_updated_by   = "[email protected]"
        created_or_updated_time = "2020-Jul-16 15:34:02 UTC"
        enabled                 = true
        id                      = "TECHALLY_1234"
        intg_guid               = "TECHALLY_1234"
        name                    = "TF audit_log"
        org_level               = false
        resource_id             = "demo"
        resource_level          = "PROJECT"
        subscription            = "projects/demo/subscriptions/lw-at-demo-lacework-subscription"
        type_name               = "GCP_AT_SES"

      ~ credentials {
            client_email   = "[email protected]"
            client_id      = "1234"
          + private_key    = (sensitive value)
            private_key_id = "abcd"
        }
    }

As a Lacework customer and a Terraform user, I want to be able to use the Lacework Terraform Provider to configure PagerDuty Alert Channels in my Lacework account, so I can configure and maintain multiple alerts as code.

provider "lacework" { }

resource "lacework_alert_channel_pagerduty" "default" {
  name               = "default alerts"
  integration_key    = "1234abc8901abc567abc123abc78e012"
}