Please note: This Terraform provider is archived, per our provider archiving process. What does this mean?
- The code repository and all commit history will still be available.
- Existing released binaries will remain available on the releases site.
- Issues and pull requests are not being monitored.
- New releases will not be published.
If anyone from the community or an interested third party is willing to maintain it, they can fork the repository and publish it to the Terraform Registry. If you are interested in maintaining this provider, please reach out to the Terraform Provider Development Program at firstname.lastname@example.org.
Terraform Provider for Hedvig
- Website: http://www.hedvig.io
- Documentation: https://www.terraform.io/docs/providers/hedvig/index.html
- Mailing list: Google Groups <img src="https://cdn.rawgit.com/hashicorp/terraform-website/master/content/source/assets/images/logo-hashicorp.svg width="600pxx">
This provider plugin is maintained by:
[Go](https://golang.org/doc/install) 1.11.0 or higher
Building the Provider
Clone repository to:
$ mkdir -p $GOPATH/src/github.com/terraform-providers; cd $GOPAth/src/github.com/terraform/providers $ git clone email@example.com:terraform-providers/terraform-provider-hedvig
Enter the provider directory and build the provider
$ cd $GOPATH/src/github.com/terraform-providers/terraform-provider-hedvig $ make build
Using the provider
See the Hedvig Provider documentation to get started using the Hedvig provider
Upgrading the provider
To upgrade to the latest stable version of the Hedvig provider run
terraform init -upgrade. See the Terraform website for more information.
Developing the Provider
If you wish to work on the provider, you'll first need Go installed on your machine (version 1.11+ is required). You'll also need to correctly setup a GOPATH, as well as adding
$GOPATH/bin to your
To compile the provider, run
make build. This will build the provider and put the provider binary in the
$ make build ... $ $GOPATH/bin/terraform-provider-hedvig ...
For guidance on common development practices such as testing changes or vendoring libraries, see the contribution guidelines. If you have other development questions we don't cover, please file an issue!