https://github.com/epilot-dev/terraform-provider-epilot-automation
Terraform provider for epilot automation API
https://github.com/epilot-dev/terraform-provider-epilot-automation
api automation epilot sdk terraform
Last synced: 2 months ago
JSON representation
Terraform provider for epilot automation API
- Host: GitHub
- URL: https://github.com/epilot-dev/terraform-provider-epilot-automation
- Owner: epilot-dev
- Created: 2023-03-13T16:39:59.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2026-03-29T00:16:44.000Z (2 months ago)
- Last Synced: 2026-03-29T03:02:31.037Z (2 months ago)
- Topics: api, automation, epilot, sdk, terraform
- Language: Go
- Homepage:
- Size: 803 KB
- Stars: 3
- Watchers: 5
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
Epilot is the digital foundation for sales, service, network and implementation processes in the context of the energy transition..
## Installation
To install this provider, copy and paste this code into your Terraform configuration. Then, run `terraform init`.
```hcl
terraform {
required_providers {
epilot-automation = {
source = "epilot-dev/epilot-automation"
version = "0.11.0"
}
}
}
provider "epilot-automation" {
server_url = "..." # Optional
}
```
## 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.
```sh
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-epilot-automation`
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/epilot-dev/epilot-automation" = ""
}
# 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 {}
}
```
## Authentication
This provider supports authentication configuration via provider configuration.
Available configuration:
| Provider Attribute | Description |
|---|---|
| `epilot_auth` | Epilot Bearer Token. |
## Available Resources and Data Sources
### Resources
* [epilot-automation_flow](docs/resources/flow.md)
### Data Sources
* [epilot-automation_flow](docs/data-sources/flow.md)
## Summary
Automation API: API Backend for epilot Automation Workflows feature
## Table of Contents
* [Installation](#installation)
* [Testing the provider locally](#testing-the-provider-locally)
* [Authentication](#authentication)
* [Available Resources and Data Sources](#available-resources-and-data-sources)
### SDK Generated by [Speakeasy](https://docs.speakeasyapi.dev/docs/using-speakeasy/client-sdks)