https://github.com/epilot-dev/terraform-provider-epilot-designbuilder
https://github.com/epilot-dev/terraform-provider-epilot-designbuilder
Last synced: 9 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/epilot-dev/terraform-provider-epilot-designbuilder
- Owner: epilot-dev
- Created: 2024-01-31T11:38:04.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2025-03-10T00:14:05.000Z (about 1 year ago)
- Last Synced: 2025-03-10T01:31:45.073Z (about 1 year ago)
- Language: Go
- Size: 393 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 XRM 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-designbuilder = {
source = "epilot-dev/epilot-designbuilder"
version = "0.14.2"
}
}
}
provider "epilot-designbuilder" {
# 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.
```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-designbuilder`
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-designbuilder" = ""
}
# 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 {}
}
```
## Available Resources and Data Sources
### Resources
* [epilot-designbuilder_design](docs/resources/design.md)
### Data Sources
* [epilot-designbuilder_design](docs/data-sources/design.md)
## Summary
## Table of Contents
* [Installation](#installation)
* [Testing the provider locally](#testing-the-provider-locally)
* [Available Resources and Data Sources](#available-resources-and-data-sources)
### SDK Generated by [Speakeasy](https://docs.speakeasyapi.dev/docs/using-speakeasy/client-sdks)