https://github.com/springernature/terraform-provider-ee-platform
Terraform Provider for the EE Platform
https://github.com/springernature/terraform-provider-ee-platform
engineering-enablement
Last synced: 3 months ago
JSON representation
Terraform Provider for the EE Platform
- Host: GitHub
- URL: https://github.com/springernature/terraform-provider-ee-platform
- Owner: springernature
- License: mpl-2.0
- Created: 2024-09-25T09:44:35.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2024-12-11T23:56:05.000Z (6 months ago)
- Last Synced: 2025-01-10T14:32:31.666Z (5 months ago)
- Topics: engineering-enablement
- Language: Go
- Homepage: https://registry.terraform.io/providers/springernature/ee-platform
- Size: 475 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# EE Platform Terraform Provider
A Terraform Provider for working with EE platform resources.
For user documentation see the terraform registry:
https://registry.terraform.io/providers/springernature/ee-platform## Development
See the makefile commands
```shell
# configure go for private springernature modules
$ git config --global [email protected]:springernature.insteadOf https://github.com/springernature
$ go env -w GOPRIVATE=github.com/springernature/*# run the tests
$ make test# build the binary in your $GOHOME/bin
$ make install# tell terraform to use this binary instead of from the actual registry
$ cat ~/.terraformrc
provider_installation {dev_overrides {
"registry.terraform.io/springernature/ee-platform" = "/Users//go/bin/"
}# 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 {}
}# run the example
$ cd examples/data-sources/ee-platform_teams
$ terraform init && terraform plan
```## Releasing
[](https://github.com/springernature/terraform-provider-ee-platform/actions/workflows/release.yml)
To publish a new release, create a git tag in the semver format `vx.y.z`. The workflow will run which creates a github release and updates the terraform registry.
```shell
$ git tag -a v0.0.2 -m "message"
$ git push --tags
```