You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ provider "env0" {
70
70
### Run local version of the provider
71
71
- Build - `./build.sh`
72
72
- Create the plugins folder - `mkdir -p ~/.terraform.d/plugins/terraform.env0.com/local/env0/6.6.6/darwin_amd64`
73
-
- Copy the built binary - `cp ~/env0/terraform-provider-env0/terraform-provider-env0 ~/.terraform.d/plugins/terraform.env0.com/local/env0/6.6.6/darwin_amd64` (Replace `darwin` with `linux` on Linux)
73
+
- Copy the built binary - `cp ./terraform-provider-env0 ~/.terraform.d/plugins/terraform.env0.com/local/env0/6.6.6/darwin_amd64` (Replace `darwin` with `linux` on Linux)
74
74
- Require the local provider in your `main.tf` -
75
75
```
76
76
terraform {
@@ -132,12 +132,12 @@ go generate ./...
132
132
133
133
## Documentation
134
134
- Docs are generated using github.com/hashicorp/terraform-plugin-docs
135
-
- Run `./generate-docs` to generate docs
135
+
- Run `./generate-docs.sh` to generate docs
136
136
- Must be run manually before releasing a version
137
137
138
138
## Release
139
139
To release a version to the [Terraform Public Registry](https://registry.terraform.io/providers/env0/env0/latest?pollNotifications=true) -
140
-
1. Docs must be generated manually and committed to the repo before release. (`./generate-docs`)
140
+
1. Docs must be generated manually and committed to the repo before release. (`./generate-docs.sh`)
141
141
2. Create and push a tag locally, in semver format - `git tag v0.0.9 && git push origin --tags`
142
142
3. Goto [Github Releases](https://github.com/env0/terraform-provider-env0/releases) and edit the draft created by Release Drafter Bot - it should contain the change log for the release. Make sure it's pointing at the tag you created in the previous step and publish the release.
143
143
4. Binaries will be automatically generated by the Github action defined in `.github/workflows/release.yml`
0 commit comments