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: website/docs/index.html.markdown
+23-11
Original file line number
Diff line number
Diff line change
@@ -8,19 +8,23 @@ description: |-
8
8
9
9
# OVH Provider
10
10
11
-
The OVH provider is the entry point to interact with the resources provided by OVHcloud.
11
+
The OVH provider is the entry point to interact with the resources provided by OVHcloud.
12
12
13
-
-> __NOTE__ According on your needs, you may need to use additional providers. This [documentation page](https://help.ovhcloud.com/csm/en-gb-terraform-at-ovhcloud?id=kb_article_view&sysparm_article=KB0054612) provides the mapping between the control panel concepts and the terraform providers / ressources.
13
+
-> __NOTE__ According on your needs, you may need to use additional providers. This [documentation page](https://help.ovhcloud.com/csm/en-gb-terraform-at-ovhcloud?id=kb_article_view&sysparm_article=KB0054612) provides the mapping between the control panel concepts and the terraform providers / resources.
14
14
15
15
Use the navigation to the left to read about the available resources.
16
16
17
17
## Provider configuration
18
18
19
19
The provider needs to be configured with the proper credentials before it can be used. Requests to OVHcloud APIs require a set of secrets keys and the definition of the API end point. See [First Steps with the API](https://docs.ovh.com/gb/en/customer/first-steps-with-ovh-api/) (or the French version, [Premiers pas avec les API OVHcloud](https://docs.ovh.com/fr/api/api-premiers-pas/)) for a detailed explanation.
20
20
21
-
Two forms of authentication are supported by the provider:
22
-
- OAuth2, using scopped service accounts, and compatible with OVHcloud IAM
@@ -51,7 +55,7 @@ Alternatively it is suggested to use configuration files or environment
51
55
variables so that the same code may run seamlessly in multiple environments.
52
56
Production and development for instance.
53
57
54
-
The provider will first look for direct instanciation parameters then
58
+
The provider will first look for direct instantiation parameters then
55
59
``OVH_ENDPOINT``, ``OVH_CLIENT_ID`` and ``OVH_CLIENT_SECRET`` environment variables.
56
60
If either of these parameter is not provided, it will look for a configuration file of the form:
57
61
@@ -83,10 +87,18 @@ project or user.
83
87
84
88
You can find more details about the configuration parsing on repository [go-ovh](https://github.com/ovh/go-ovh).
85
89
90
+
### Access token
91
+
92
+
The provider will look for the token either at ``OVH_ACCESS_TOKEN`` environment
93
+
variable, or get it via ``access_token`` argument in the provider's stanza.
94
+
95
+
Similarly to OAuth2 method, the endpoint must be configured (either via
96
+
``endpoint`` argument, or with ``OVH_ENDPOINT`` environment variable).
97
+
86
98
### Application Key/Application Secret
87
99
88
100
The required keys are the `application_key`, the `application_secret`, and the `consumer_key`.
89
-
These keys can be generated via the [OVHcloud token generation page](https://api.ovh.com/createToken/?GET=/*&POST=/*&PUT=/*&DELETE=/*).
101
+
These keys can be generated via the [OVHcloud token generation page](https://api.ovh.com/createToken/?GET=/*&POST=/*&PUT=/*&DELETE=/*).
90
102
91
103
These parameters can be configured directly in the provider block as shown hereafter.
92
104
@@ -113,7 +125,7 @@ Alternatively it is suggested to use configuration files or environment
113
125
variables so that the same code may run seamlessly in multiple environments.
114
126
Production and development for instance.
115
127
116
-
The provider will first look for direct instanciation parameters then
128
+
The provider will first look for direct instantiation parameters then
117
129
``OVH_ENDPOINT``, ``OVH_APPLICATION_KEY``, ``OVH_APPLICATION_SECRET`` and
118
130
``OVH_CONSUMER_KEY`` environment variables. If either of these parameter is not
119
131
provided, it will look for a configuration file of the form:
@@ -246,12 +258,12 @@ variables must also be set:
246
258
247
259
*`OVH_CLOUD_PROJECT_FAILOVER_IP_ROUTED_TO_1_TEST` - The GUID of an instance to which failover IP addresses can be attached
248
260
249
-
*`OVH_CLOUD_PROJECT_FAILOVER_IP_ROUTED_TO_2_TEST` - The GUID of a secondary instance to which failover IP addresses can be attached. There must be 2 as associations can only be updated not removed. To test effectively, the failover ip address must be moved between instances
261
+
*`OVH_CLOUD_PROJECT_FAILOVER_IP_ROUTED_TO_2_TEST` - The GUID of a secondary instance to which failover IP addresses can be attached. There must be 2 as associations can only be updated not removed. To test effectively, the failover ip address must be moved between instances
250
262
251
263
*`OVH_CLOUD_PROJECT_KUBE_REGION_TEST` - The region of your public cloud kubernetes project.
252
264
253
265
*`OVH_CLOUD_PROJECT_KUBE_VERSION_TEST` - The version of your public cloud kubernetes project.
254
-
*`OVH_CLOUD_PROJECT_KUBE_PREV_VERSION_TEST` - The previous version of your public cloud kubernetes project. This is used to test upgrade.
266
+
*`OVH_CLOUD_PROJECT_KUBE_PREV_VERSION_TEST` - The previous version of your public cloud kubernetes project. This is used to test upgrade.
255
267
256
268
*`OVH_DEDICATED_SERVER` - The name of the dedicated server to test dedicated_server_networking resource.
257
269
@@ -260,7 +272,7 @@ variables must also be set:
260
272
*`OVH_ZONE_TEST` - The domain you own to test the domain_zone resource.
261
273
262
274
*`OVH_IP_TEST`, `OVH_IP_BLOCK_TEST`, `OVH_IP_REVERSE_TEST` - The values you have to set for testing ip reverse resources.
263
-
275
+
264
276
*`OVH_IP_MOVE_SERVICE_NAME_TEST` - The value you have to set for testing ip move resources.
265
277
266
278
*`OVH_DBAAS_LOGS_SERVICE_TEST` - The name of your Dbaas logs service.
0 commit comments