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: docs/guides/installation.md
+25-25Lines changed: 25 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,8 @@
1
-
# Automatic Registry Installation
1
+
# Installation
2
+
3
+
This document describes how to install the Terraform provider.
4
+
5
+
## Automatic Registry Installation
2
6
3
7
To install this provider, copy and paste this code into your Terraform configuration (include a version tag).
4
8
@@ -19,23 +23,23 @@ provider "proxmox" {
19
23
20
24
Then, run
21
25
22
-
```shell
23
-
$ terraform init
26
+
```bash
27
+
terraform init
24
28
```
25
29
26
-
# Manual Build & Install
30
+
##Manual Build & Install
27
31
28
32
When developing this provider, it's useful to bootstrap a development as quick as possible. You can use
29
33
the [Proxmox VE vagrant VM](https://github.com/rgl/proxmox-ve) project for instance. Check out
30
34
the [examples](../../examples/vagrant_example.tf) for a `main.tf` to use.
31
35
32
-
## How to get terraform to recognize third party provider
36
+
###How to get terraform to recognize third party provider
33
37
34
38
Third-party plugins can be manually installed into the user plugins directory, located
35
39
at `%APPDATA%\terraform.d\plugins` on Windows and `~/.terraform.d/plugins` on other systems. Plugins come with
36
40
executables that have to be placed in the plugin directory.
37
41
38
-
## Compile the executables with Go
42
+
###Compile the executables with Go
39
43
40
44
First, clone this repo and cd into the repo's root.
41
45
@@ -49,48 +53,45 @@ you want an automated way to do it, look at go.yml in the root of this repo.
49
53
50
54
Then to compile the provider:
51
55
52
-
```shell
56
+
```bash
53
57
make
54
58
```
55
59
56
60
The executable will be in the `./bin` directory.
57
61
58
-
## Copy executables to plugin directory (Terraform >=0.13)
62
+
###Copy executables to plugin directory (Terraform >=0.13)
59
63
60
64
As of Terraform v0.13, locally-installed, third-party plugins
61
-
must [conform to a new filesystem layout](https://github.com/hashicorp/terraform/blob/guide-v0.13-beta/draft-upgrade-guide.md#new-filesystem-layout-for-local-copies-of-providers)
62
-
.
65
+
must [conform to a new filesystem layout](https://github.com/hashicorp/terraform/blob/guide-v0.13-beta/draft-upgrade-guide.md#new-filesystem-layout-for-local-copies-of-providers).
63
66
64
67
> Terraform assumes that a provider without an explicit source address belongs to the "hashicorp" namespace on registry.terraform.io, which is not true for your in-house provider. Instead, you can use any domain name under your control to establish a virtual source registry to serve as a separate namespace for your local use.
65
68
66
69
Use the format: [host.domain]/telmate/proxmox/[version]/[arch].
67
70
68
71
In our case, we will use `registry.example.com` as our virtual source registry in the following examples.
69
72
70
-
```shell
73
+
```bash
71
74
# Uncomment for macOS
72
75
# PLUGIN_ARCH=darwin_amd64
73
76
74
-
$ PLUGIN_ARCH=linux_amd64
77
+
PLUGIN_ARCH=linux_amd64
75
78
76
79
# Create the directory holding the newly built Terraform plugins
0 commit comments