Merge pull request #26 from dlecan/patch-1

Improve initial description of OVH provider setup

Author: yanndegat

website/docs/index.html.markdown

@@ -14,27 +14,49 @@ with the proper credentials before it can be used.
 
 Use the navigation to the left to read about the available resources.
 
-## Example Usage
+## Configuration of the provider
+
+Requests to OVH APIs need to configure secrets keys in the provider, either fetching them from `~/.ovh.conf` file, in configuration of OVH provider or from your environment.
+
+It is recommend to install [ovh-cli](https://github.com/ovh/ovh-cli) to handle and manage all your secret keys.
+
+Follow [installation](https://github.com/ovh/ovh-cli#installation) then [setup](https://github.com/ovh/ovh-cli#getting-started) steps of ovh-cli to initialize your environment (secret keys and `~/.ovh.conf` file).
+
+Then, you can just declare a minimal configuration of the OVH provider:
 
+```hcl
+# Configure the OVH Provider
+provider "ovh" {
+  endpoint = "ovh-eu"
+}
 ```
+Secret keys `endpoint`, `application_key`, `application_secret` or
+`consumer_key` will be fetched from the `~/.ovh.conf` file.
+
+Or you can declare them in provider configuration:
+
+```hcl
 # Configure the OVH Provider
 provider "ovh" {
   endpoint           = "ovh-eu"
   application_key    = "yyyyyy"
   application_secret = "xxxxxxxxxxxxxx"
   consumer_key       = "zzzzzzzzzzzzzz"
 }
+```
+
+Or let the provider fetching them from your environment (see "[Configuration reference](#configuration-reference)").
+
 
+## Example Usage
+
+```
 # Create a public cloud user
 resource "ovh_publiccloud_user" "user-test" {
   # ...
 }
 ```
 
-If you don't provide `endpoint`, `application_key`, `application_secret` or
-`consumer_key`, the provider will try to fetch them from the ~/.ovh.conf file
-generated by ovh-cli, or from your environment (see below).
-
 ## Configuration Reference
 
 The following arguments are supported: