From 73d9e8430aa6f7e1b1be281ffec2f129a75126dd Mon Sep 17 00:00:00 2001
From: adeniyistephen <adeniyistadz@gmail.com>
Date: Sun, 27 Dec 2020 19:43:10 +0100
Subject: [PATCH] Add hcl example for scaleway

---
 website/content/docs/builders/scaleway.mdx | 23 ++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/website/content/docs/builders/scaleway.mdx b/website/content/docs/builders/scaleway.mdx
index 2dd3e64f0..b04d1a99e 100644
--- a/website/content/docs/builders/scaleway.mdx
+++ b/website/content/docs/builders/scaleway.mdx
@@ -53,6 +53,9 @@ can also be supplied to override the typical auto-generated key:
 Here is a basic example. It is completely valid as soon as you enter your own
 access tokens:
 
+<Tabs>
+<Tab heading="JSON">
+
 ```json
 {
   "type": "scaleway",
@@ -66,6 +69,26 @@ access tokens:
   "ssh_private_key_file": "~/.ssh/id_rsa"
 }
 ```
+</Tab>
+
+<Tab heading="HCL2">
+
+```hcl
+builders "scaleway" {
+  type = "scaleway"
+  project_id = "YOUR PROJECT ID"
+  access_key = "YOUR ACCESS KEY"
+  secret_key = "YOUR SECRET KEY"
+  image = "UUID OF THE BASE IMAGE"
+  zone = "fr-par-1"
+  commercial_type = "DEV1-S"
+  ssh_username = "root"
+  ssh_private_key_file = "~/.ssh/id_rsa"
+}
+```
+</Tab>
+</Tabs>
+
 
 When you do not specify the `ssh_private_key_file`, a temporary SSH keypair
 is generated to connect the server. This key will only allow the `root` user to