All existing pre-built providers will be relocating to our new Github organization cdktf
.
For the vast majority of CDKTF users, this won’t affect how you reference the providers, as you’re consuming them through your language-specific package manager: NPM, PyPI, Maven, etc. However, for Golang users of CDKTF, this is something to be aware of. Soon, the module naming will switch from:
github.com/hashicorp/cdktf-provider-{provider name}-go
to
github.com/cdktf/cdktf-provider-{provider name}-go
There is no need for any immediate action, but over the course of the next few days if you see the Go CLI complain about:
go: github.com/hashicorp/cdktf-provider-hashicups-go/hashicups@v0.0.3: parsing go.mod:
module declares its path as: github.com/cdktf/cdktf-provider-hashicups-go/hashicups
but was required as: github.com/hashicorp/cdktf-provider-hashicups-go/hashicups
Regarding one or more of the pre-built providers, change the module path to the one with github.com/cdktf
.
You could also use Go tools to do the replace for you (replace hashicups
with your provider):
$ gofmt -w -r '"github.com/hashicorp/cdktf-provider-hashicups-go/hashicups" -> "github.com/cdktf/cdktf-provider-hashicups-go/hashicups"' ./
$ go get # Fetch the prebuilt provider from the new module path
$ go mod tidy # Remove old module path
As another example, if you were using the AWS provider, the first command above becomes:
$ gofmt -w -r '"github.com/hashicorp/cdktf-provider-aws-go/aws/v9" -> "github.com/cdktf/cdktf-provider-aws-go/aws/v9"' ./