From 7a04b53571de2ede6d3ca7d50eeabe40412ccfa8 Mon Sep 17 00:00:00 2001
From: Nathan Rodet <nrodet@grandlyon.com>
Date: Fri, 20 Jan 2023 10:19:26 +0100
Subject: [PATCH] Change to hash creation with argon

---
 README.md | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index c3386ae..b246625 100644
--- a/README.md
+++ b/README.md
@@ -57,7 +57,7 @@ Template are available to the link below.
 In this example, you will find how to create a file to a defined path with cloud-init.
 Content inside `%` are meant to be replaced with sed command to be able to use environment variables or user-data.
 
-**example:**
+**Example:**
 ```yaml
 write_files:
   - content: |
@@ -94,7 +94,7 @@ sed -i "s/%atrium_count_index%/$(scw-userdata atrium_count_index)/g" /root/atriu
 
 The example show how to curl a configuration file from repository to a defined path with cloud-init.
 
-**example :**
+**Example :**
 ```yaml
 runcmd:
 #
@@ -111,11 +111,10 @@ runcmd:
 
 ## Use Gitlab variables in instances
 
-### Example
-
 From my instances, I should be able to access the variables as user-data using the command `scw-userdata <my-variable>` after declaring them in Terraform.
 **Some documentation : https://blog.scaleway.com/introducing-scaleway-cloud-init-support/**
 
+**Example : Declare in Terraform**
 ```HCL
 user_data = {
     atrium_count_index = count.index
@@ -126,6 +125,11 @@ user_data = {
 }
 ```
 
+** Example : Retrieve in instance
+```bash
+scw-userdata atrium_count_index
+```
+
 ## Setup Terraform Locally
 
 First, you must setup 2 local files for your variables :
@@ -164,7 +168,7 @@ Now, you can create a file for your variables information called **variables-loc
 SCW_PROJECT_ID         = ""
 SCW_ACCESS_KEY         = ""
 SCW_SECRET_KEY         = ""
-INSTANCES_COUNT        = "2"
+INSTANCES_COUNT        = ""
 ENVIRONMENT            = ""
 ```
 
-- 
GitLab