Add scaleway provider (#7331)

* Add scaleway provider

this PR allows the entire scaleway stack to be managed with terraform

example usage looks like this:

```
provider "scaleway" {
  api_key = "snap"
  organization = "snip"
}

resource "scaleway_ip" "base" {
  server = "${scaleway_server.base.id}"
}

resource "scaleway_server" "base" {
  name = "test"
  # ubuntu 14.04
  image = "aecaed73-51a5-4439-a127-6d8229847145"
  type = "C2S"
}

resource "scaleway_volume" "test" {
  name = "test"
  size_in_gb = 20
  type = "l_ssd"
}

resource "scaleway_volume_attachment" "test" {
  server = "${scaleway_server.base.id}"
  volume = "${scaleway_volume.test.id}"
}

resource "scaleway_security_group" "base" {
  name = "public"
  description = "public gateway"
}

resource "scaleway_security_group_rule" "http-ingress" {
  security_group = "${scaleway_security_group.base.id}"

  action = "accept"
  direction = "inbound"
  ip_range = "0.0.0.0/0"
  protocol = "TCP"
  port = 80
}

resource "scaleway_security_group_rule" "http-egress" {
  security_group = "${scaleway_security_group.base.id}"

  action = "accept"
  direction = "outbound"
  ip_range = "0.0.0.0/0"
  protocol = "TCP"
  port = 80
}
```

Note that volume attachments require the server to be stopped, which can lead to
downtimes of you attach new volumes to already used servers

* Update IP read to handle 404 gracefully

* Read back resource on update

* Ensure IP detachment works as expected

Sadly this is not part of the official scaleway api just yet

* Adjust detachIP helper

based on feedback from @QuentinPerez in
scaleway/scaleway-cli#378

* Cleanup documentation

* Rename api_key to access_key

following @stack72 suggestion and rename the provider api_key for more clarity

* Make tests less chatty by using custom logger

Author: nicolai86

index.html.markdown

@@ -0,0 +1,90 @@
+---
+layout: "scaleway"
+page_title: "Provider: Scaleway"
+sidebar_current: "docs-scaleway-index"
+description: |-
+  The Scaleway provider is used to interact with Scaleway ARM cloud provider.
+---
+
+# Scaleway Provider
+
+The Scaleway provider is used to manage Scaleway resources.
+
+Use the navigation to the left to read about the available resources.
+
+## Example Usage
+
+Here is an example that will setup the following:
++ An ARM Server.
++ An IP Address.
++ A security group.
+
+(create this as sl.tf and run terraform commands from this directory):
+
+```hcl
+provider "scaleway" {
+  access_key = ""
+  organization = ""
+}
+
+resource "scaleway_ip" "ip" {
+  server = "${scaleway_server.test.id}"
+}
+
+resource "scaleway_server" "test" {
+  name = "test"
+  image = "aecaed73-51a5-4439-a127-6d8229847145"
+  type = "C2S"
+}
+
+resource "scaleway_volume" "test" {
+  name = "test"
+  size_in_gb = 20
+  type = "l_ssd"
+}
+
+resource "scaleway_volume_attachment" "test" {
+  server = "${scaleway_server.test.id}"
+  volume = "${scaleway_volume.test.id}"
+}
+
+resource "scaleway_security_group" "http" {
+  name = "http"
+  description = "allow HTTP and HTTPS traffic"
+}
+
+resource "scaleway_security_group_rule" "http_accept" {
+  security_group = "${scaleway_security_group.http.id}"
+
+  action = "accept"
+  direction = "inbound"
+  ip_range = "0.0.0.0/0"
+  protocol = "TCP"
+  dest_port_from = 80
+}
+
+resource "scaleway_security_group_rule" "https_accept" {
+  security_group = "${scaleway_security_group.http.id}"
+
+  action = "accept"
+  direction = "inbound"
+  ip_range = "0.0.0.0/0"
+  protocol = "TCP"
+  dest_port_from = 443
+}
+
+```
+
+You'll need to provide your Scaleway organization and access key,
+so that Terraform can connect. If you don't want to put
+credentials in your configuration file, you can leave them
+out:
+
+```
+provider "scaleway" {}
+```
+
+...and instead set these environment variables:
+
+- **SCALEWAY_ORGANIZATION**: Your Scaleway organization
+- **SCALEWAY_ACCESS_KEY**: Your API Access key

r/ip.html.markdown

@@ -0,0 +1,34 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: ip"
+sidebar_current: "docs-scaleway-resource-ip"
+description: |-
+  Manages Scaleway IPs.
+---
+
+# scaleway\ip
+
+Provides IPs for ARM servers. This allows IPs to be created, updated and deleted.
+For additional details please refer to [API documentation](https://developer.scaleway.com/#ips).
+
+## Example Usage
+
+```
+resource "scaleway_ip" "test_ip" {
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `server` - (Optional) ID of ARM server to associate IP with
+
+Field `server` are editable.
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource
+* `ip` - IP of the new resource

r/security_group.html.markdown

@@ -0,0 +1,36 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: security_group"
+sidebar_current: "docs-scaleway-resource-security_group"
+description: |-
+  Manages Scaleway security groups.
+---
+
+# scaleway\security_group
+
+Provides security groups. This allows security groups to be created, updated and deleted.
+For additional details please refer to [API documentation](https://developer.scaleway.com/#security-groups).
+
+## Example Usage
+
+```
+resource "scaleway_security_group" "test" {
+  name = "test"
+  description = "test"
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `name` - (Required) name of security group
+* `description` - (Required) description of security group
+
+Field `name`, `description` are editable.
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource

r/security_group_rule.html.markdown

@@ -0,0 +1,51 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: security_group_rule"
+sidebar_current: "docs-scaleway-resource-security_group_rule"
+description: |-
+  Manages Scaleway security group rules.
+---
+
+# scaleway\security_group_rule
+
+Provides security group rules. This allows security group rules to be created, updated and deleted.
+For additional details please refer to [API documentation](https://developer.scaleway.com/#security-groups-manage-rules).
+
+## Example Usage
+
+```
+resource "scaleway_security_group" "test" {
+  name = "test"
+  description = "test"
+}
+
+resource "scaleway_security_group_rule" "smtp_drop_1" {
+  security_group = "${scaleway_security_group.test.id}"
+
+  action = "accept"
+  direction = "inbound"
+  ip_range = "0.0.0.0/0"
+  protocol = "TCP"
+  dest_port_from = 25
+}
+
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `action` - (Required) action of rule (`accept`, `drop`)
+* `direction` - (Required) direction of rule (`inbound`, `outbound`)
+* `ip_range` - (Required) ip_range of rule
+* `protocol` - (Required) protocol of rule (`ICMP`, `TCP`, `UDP`)
+* `dest_port_from` - (Optional) port range from
+* `dest_port_to` - (Optional) port from to
+
+Field `action`, `direction`, `ip_range`, `protocol`, `dest_port_from`, `dest_port_to` are editable.
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource

r/server.html.markdown

@@ -0,0 +1,38 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: server"
+sidebar_current: "docs-scaleway-resource-server"
+description: |-
+  Manages Scaleway servers.
+---
+
+# scaleway\server
+
+Provides ARM servers. This allows servers to be created, updated and deleted.
+For additional details please refer to [API documentation](https://developer.scaleway.com/#servers).
+
+## Example Usage
+
+```
+resource "scaleway_server" "test" {
+  name = "test"
+  image = "5faef9cd-ea9b-4a63-9171-9e26bec03dbc"
+  type = "C1"
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `name` - (Required) name of ARM server
+* `image` - (Required) base image of ARM server
+* `type` - (Required) type of ARM server
+
+Field `name`, `type` are editable.
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource

r/volume.html.markdown

@@ -0,0 +1,44 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: volume"
+sidebar_current: "docs-scaleway-resource-volume"
+description: |-
+  Manages Scaleway Volumes.
+---
+
+# scaleway\volume
+
+Provides ARM volumes. This allows volumes to be created, updated and deleted.
+For additional details please refer to [API documentation](https://developer.scaleway.com/#volumes).
+
+## Example Usage
+
+```
+resource "scaleway_volume" "test" {
+  name = "test"
+  image = "aecaed73-51a5-4439-a127-6d8229847145"
+  type = "C2S"
+  volumes = ["${scaleway_volume.test.id}"]
+}
+
+resource "scaleway_volume" "test" {
+  name = "test"
+  size_in_gb = 20
+  type = "l_ssd"
+}
+
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `name` - (Required) name of volume
+* `size_in_gb` - (Required) size of the volume in GB
+* `type` - (Required) type of volume
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource

r/volume_attachment.html.markdown

@@ -0,0 +1,48 @@
+---
+layout: "scaleway"
+page_title: "Scaleway: volume attachment"
+sidebar_current: "docs-scaleway-resource-volume attachment"
+description: |-
+  Manages Scaleway Volume attachments for servers.
+---
+
+# scaleway\volume\_attachment
+
+This allows volumes to be attached to servers.
+
+**Warning:** Attaching volumes requires the servers to be powered off. This will lead
+to downtime if the server is already in use.
+
+## Example Usage
+
+```
+resource "scaleway_server" "test" {
+  name = "test"
+  image = "aecaed73-51a5-4439-a127-6d8229847145"
+  type = "C2S"
+}
+
+resource "scaleway_volume" "test" {
+  name = "test"
+  size_in_gb = 20
+  type = "l_ssd"
+}
+
+resource "scaleway_volume_attachment" "test" {
+  server = "${scaleway_server.test.id}"
+  volume = "${scaleway_volume.test.id}"
+}
+```
+
+## Argument Reference
+
+The following arguments are supported:
+
+* `server` - (Required) id of the server
+* `volume` - (Required) id of the volume to be attached
+
+## Attributes Reference
+
+The following attributes are exported:
+
+* `id` - id of the new resource