ConductorOne Terraform Provider

Usage

See the docs for usage information

Testing the provider locally

Should you want to validate a change locally, the --debug flag allows you to execute the provider against a terraform instance locally.

This also allows for debuggers (e.g. delve) to be attached to the provider.

go run main.go --debug
# Copy the TF_REATTACH_PROVIDERS env var
# In a new terminal
cd examples/your-example
TF_REATTACH_PROVIDERS=... terraform init
TF_REATTACH_PROVIDERS=... terraform apply

Authentication

This provider supports authentication configuration via provider configuration.

Available configuration:

Provider Attribute	Description
bearer_auth	HTTP Bearer.
oauth	This API uses OAuth2 with the Client Credential flow.
Client Credentials must be sent in the BODY, not the headers.
For an example of how to implement this, refer to the c1TokenSource.Token() function..

Available Resources and Data Sources

Resources

• conductorone_access_conflict
• conductorone_access_profile
• conductorone_access_profile_requestable_entries
• conductorone_access_profile_visibility_bindings
• conductorone_app
• conductorone_app_entitlement_automation
• conductorone_app_entitlement_proxy_binding
• conductorone_app_resource
• conductorone_app_resource_type
• conductorone_app_entitlement_monitor_binding
• conductorone_app_entitlement_owner
• conductorone_app_owner
• conductorone_app_resource_owner
• conductorone_automation
• conductorone_bundle_automation
• conductorone_compliance_framework
• conductorone_connector_credential
• conductorone_custom_app_entitlement
• conductorone_function
• conductorone_function_commit
• conductorone_function_tag
• conductorone_policy
• conductorone_request_schema_entitlement_binding
• conductorone_request_schema
• conductorone_risk_level
• conductorone_webhook

Data Sources

• conductorone_access_profile
• conductorone_app
• conductorone_app_entitlement
• conductorone_app_entitlement_automation
• conductorone_app_entitlement_proxy_binding
• conductorone_app_entitlements
• conductorone_app_resource
• conductorone_app_resource_type
• conductorone_app_resource_types
• conductorone_app_resources
• conductorone_app_entitlement_monitor_binding
• conductorone_apps
• conductorone_aws_external_id
• conductorone_bundle_automation
• conductorone_compliance_framework
• conductorone_compliance_frameworks
• conductorone_connector_credential
• conductorone_function
• conductorone_function_commit
• conductorone_function_tag
• conductorone_policies
• conductorone_policy
• conductorone_request_catalogs
• conductorone_request_schema_entitlement_binding
• conductorone_request_schema
• conductorone_risk_level
• conductorone_risk_levels
• conductorone_user
• conductorone_users
• conductorone_webhook
• conductorone_webhooks

Terraform allows you to use local provider builds by setting a dev_overrides block in a configuration file called .terraformrc. This block overrides all other configured installation methods.

Terraform searches for the .terraformrc file in your home directory and applies any configuration settings you set.

provider_installation {

  dev_overrides {
      "registry.terraform.io/terraform/scaffolding" = "<PATH>"
  }

  # For all other providers, install them directly from their origin provider
  # registries as normal. If you omit this, Terraform will _only_ use
  # the dev_overrides block, and so no other providers will be available.
  direct {}
}

Your <PATH> may vary depending on how your Go environment variables are configured. Execute go env GOBIN to set it, then set the <PATH> to the value returned. If nothing is returned, set it to the default location, $HOME/go/bin.

Versions with breaking changes

v1.0.0

• This version introduces a breaking change to the request_catalog resource and datasource. The request_catalog resource and datasource are now the access_profile resource and datasource.
• There are also breaking changes to many of the datasources, as we switched to using search endpoints to give more options on how to filter the result. This may require you to update your Terraform configurations to use the proper fields for the datasources as some of the field names have changed.

v0.4.0

• This version fixes issues with importing app entitlements. The SDK and the provider schema did not match so imports were broken, the provider was changed to match the SDK which introduced a breaking change. the max_grant_druation object was removed and the internal duration_unset and grant_unset fields have been moved out.

v0.3.0

• This version fixes issue where you weren't able to update app owners on the app resource by breaking out app owners into it's own resource. This will break any Terraform configurations that specify appOwners on the app resource. To use the new version of the provider you will need to use the new app_owners resource to configure the owners of an app, and no longer specify owners on the app resource.

v0.2.0

• This version introduces a breaking change to the app_entitlement datasource. The app_entitlement datasource now nests the grant_duration and grant_unset inside the max_grant_duration field.

v0.1.0

• This version introduces a breaking change to the app_entitlement_owners resource. The app_entitlement_owners resource now requires a list of strings called user_ids, which is used to set the owners on the resource. The list of user_ids will replace any existing owners on the app entitlement with the new list of owners.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Feel free to open a PR or a Github issue as a proof of concept and we'll do our best to include it in a future release !

SDK Created by Speakeasy

Summary

ConductorOne API: The ConductorOne API is a HTTP API for managing ConductorOne resources.

Table of Contents

• ConductorOne Terraform Provider
  • Usage
  • Testing the provider locally
  • Authentication
  • Available Resources and Data Sources
  • Versions with breaking changes
  • Contributions
  • Installation
  • Testing the provider locally

Installation

To install this provider, copy and paste this code into your Terraform configuration. Then, run terraform init.

terraform {
  required_providers {
    conductorone = {
      source  = "conductorone/conductorone"
      version = "1.6.15"
    }
  }
}

provider "conductorone" {
  # Configuration options
}

Testing the provider locally

Local Provider

Should you want to validate a change locally, the --debug flag allows you to execute the provider against a terraform instance locally.

This also allows for debuggers (e.g. delve) to be attached to the provider.

go run main.go --debug
# Copy the TF_REATTACH_PROVIDERS env var
# In a new terminal
cd examples/your-example
TF_REATTACH_PROVIDERS=... terraform init
TF_REATTACH_PROVIDERS=... terraform apply

Compiled Provider

Terraform allows you to use local provider builds by setting a dev_overrides block in a configuration file called .terraformrc. This block overrides all other configured installation methods.

1. Execute go build to construct a binary called terraform-provider-conductorone
2. Ensure that the .terraformrc file is configured with a dev_overrides section such that your local copy of terraform can see the provider binary

Terraform searches for the .terraformrc file in your home directory and applies any configuration settings you set.

provider_installation {

  dev_overrides {
      "registry.terraform.io/conductorone/conductorone" = "<PATH>"
  }

  # For all other providers, install them directly from their origin provider
  # registries as normal. If you omit this, Terraform will _only_ use
  # the dev_overrides block, and so no other providers will be available.
  direct {}
}