Resource: splunk_generic_acl

Manage the ACL of any Splunk object not already managed in Terraform. To define the ACL of an object that is itself managed in Terraform, use the acl block on that configured resource instead of using a splunk_generic_acl resource.

Note: This resource doesn't actually create any remote resources, because ACLs can only exist (and always exist) for knowledge objects. They can, however, be managed separately.

Example Usage

resource "splunk_generic_acl" "my_app" {
  # apps are managed via the apps/local/<app> endpoint
  path = "apps/local/my_app"
  acl {
    # use app=system, owner=nobody when managing apps, as they have no owner or app context
    app   = "system"
    owner = "nobody"
    read  = ["*"]
    write = ["admin", "power"]
  }
}

resource "splunk_generic_acl" "my_dashboard" {
  path = "data/ui/views/my_dashboard"
  acl {
    app   = "my_app"
    owner = "joe_user"
    read  = ["team_joe"]
    write = ["team_joe"]
  }
}

Argument Reference

For latest resource argument reference: https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTapps#apps.2Flocal

This resource block supports the following arguments:

Attribute Reference

In addition to all arguments above, This resource block exports the following arguments:

Import

Generic ACL resources can be imported by specifying their owner, app, and path with a colon-delimited string as the ID:

terraform import splunk_generic_acl <owner>:<app>:<path>