5 ms·

Even though this will likely prevent OpenTF from connecting to registry.terraform.io to get plugins, the source code for most (all?) plugins is still open sourc

Even though this will likely prevent OpenTF from connecting to registry.terraform.io to get plugins, the source code for most (all?) plugins is still open source and actually stored on GitHub (e.g. https://github.com/terraform-provider-openstack/terraform-provider-openstack https://github.com/terraform-provider-openstack/terraform-pr...). More work for OpenTF to get up and running, but also feels reasonable that HashiCorp wouldn't allow connecting to their service.

tyingq 3y ago
>still open source and actually stored on GitHub I think that's true, but it's probably hard to recreate large parts of the index. I don't think there's any mandatory manifest or something like that where you can reliably identify a repo as something that appears in their registry. Probably some missing metadata too.
- fishnchips 3y ago
  The publishing process for the public registry is very prescriptive, and there is indeed a manifest file involved - https://developer.hashicorp.com/terraform/registry/providers/publishing https://developer.hashicorp.com/terraform/registry/providers...
  - tyingq 3y ago
    That helps, but it reads like the manifest is optional.
    - fishnchips 3y ago
      Correct, the manifest is optional.
- ashald 3y ago
  It's... effort consuming, but is doable and more like a 1-time effort. A while ago I built an alternative plugin manager for Terraform (https://github.com/paraterraform/para https://github.com/paraterraform/para) and explored the idea of distributed indices (where you just host a file in the repo as seen in https://github.com/ashald/terraform-provider-stateful/blob/master/provider.stateful.yaml https://github.com/ashald/terraform-provider-stateful/blob/m...). So at the end of the day, it's either about the effort to inventory the current registry and find sources that are available, or do this on an ongoing as-needed basis (eg something like para would allow an index to be hosted in a github repo managed with PRs).

tyingq 3y ago

>still open source and actually stored on GitHub I think that's true, but it's probably hard to recreate large parts of the index. I don't think there's any mandatory manifest or something like that where you can reliably identify a repo as something that appears in their registry. Probably some missing metadata too.

fishnchips 3y ago
The publishing process for the public registry is very prescriptive, and there is indeed a manifest file involved - https://developer.hashicorp.com/terraform/registry/providers/publishing https://developer.hashicorp.com/terraform/registry/providers...
- tyingq 3y ago
  That helps, but it reads like the manifest is optional.
  - fishnchips 3y ago
    Correct, the manifest is optional.
ashald 3y ago
It's... effort consuming, but is doable and more like a 1-time effort. A while ago I built an alternative plugin manager for Terraform (https://github.com/paraterraform/para https://github.com/paraterraform/para) and explored the idea of distributed indices (where you just host a file in the repo as seen in https://github.com/ashald/terraform-provider-stateful/blob/master/provider.stateful.yaml https://github.com/ashald/terraform-provider-stateful/blob/m...). So at the end of the day, it's either about the effort to inventory the current registry and find sources that are available, or do this on an ongoing as-needed basis (eg something like para would allow an index to be hosted in a github repo managed with PRs).