hashicorp/terraform-provider-ecl

Terraform EnterpriseCloud provider. Please note: This Terraform provider is archived per our provider archiving process: https://terraform.io/docs/internals/archiving.html

Please note: This Terraform provider is archived, per our provider archiving process. What does this mean?

1. The code repository and all commit history will still be available.
2. Existing released binaries will remain available on the releases site.
3. Issues and pull requests are not being monitored.
4. 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 [email protected].

Terraform Enterprise Cloud Provider

Maintainers

This provider plugin is maintained by:

• Keiichi Hikita (@keiichi-hikita)
• Takuma Watanabe (@t-wata)
• Kazunori Yoshihara (@kazyshr)
• Hitoyoshi Ohta (@htysh)

Requirements

• Terraform 0.12.x
• Go 1.13 (to build the provider plugin)

Building The Provider

Clone repository to anywhere you want:

$ git clone https://github.com/nttcom/terraform-provider-ecl 

Enter the provider directory and build the provider

$ cd terraform-provider-ecl
$ make build

Using the provider

You can browse the documentation within this repo here.

Developing the Provider

If you wish to work on the provider, you'll first need Go installed on your machine (version 1.8+ is required). You'll also need to correctly setup a GOPATH, as well as adding $GOPATH/bin to your $PATH.

To compile the provider, run make build. This will build the provider and put the provider binary in the $GOPATH/bin directory.

$ make build
...
$ cp terraform-provider-ecl $GOPATH/bin/terraform-provider-ecl
...

terraform-provider-ecl's Issues

Releases and Archive

I am a little confused by this repo. Pretty much all the other repos in the terraform-providers organization have active development within the repo itself or have been archived aka point to an external active repo.

For example, the https://github.com/terraform-providers/terraform-provider-acme repo is archived but points to an active repo where development is ongoing.

@cgriggs01 Should this repo be archived and point to their active development repo https://github.com/nttcom/terraform-provider-ecl? If not, can we see some of their releases inside that repo get merged upstream here?

@kazyshr, @shimisho and others seem to be pretty active in their releases.