From cc91937782aa84b4c1c2f7b0da93554cc58e28b1 Mon Sep 17 00:00:00 2001
From: Georgi Michev <georgi.michev@vereign.com>
Date: Wed, 8 Nov 2023 12:49:49 +0200
Subject: [PATCH] Update deployment steps

Signed-off-by: Georgi Michev <georgi.michev@vereign.com>
---
 Chart.yaml | 4 ++--
 README.md  | 7 ++++---
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/Chart.yaml b/Chart.yaml
index ac59983..cfb236f 100644
--- a/Chart.yaml
+++ b/Chart.yaml
@@ -1,6 +1,6 @@
 apiVersion: v1
-appVersion: v1.1.2
+appVersion: v1.1.3
 description: task deployment
 name: task
-version: 1.1.2
+version: 1.1.3
 icon: "https://www.vereign.com/wp-content/themes/vereign2020/images/vereign-logo.svg"
diff --git a/README.md b/README.md
index cd15006..5fd52b0 100644
--- a/README.md
+++ b/README.md
@@ -10,10 +10,11 @@ The pipeline in this repo builds image from the source code repo in eclipse as a
 
 When changes to helm or the app are made and deployment is needed, execute the following steps:
 1. Clone the repo and start working on a new branch.
-2. Execute `git submode update --remote --recursive -init` to update source to latest commit on eclipse main branch.
+1. Execute `git submodule update --remote --recursive --init` to update source to latest commit on eclipse main branch.
 1. Edit `Chart.yaml` with the new chart version (example: 1.4.3) and app version it's intended to use (example: v1.4.3).
-2. Create a new tag with the intended app version (v1.4.3)
-3. Wait for pipelines to finish and manually trigger deployment to either `dev-ssi` or `prod-ssi(vault)` clusters.
+1. Create merge request from the update branch.
+1. Create a new tag from main branch with the intended app version (v1.4.3)
+1. Wait for pipelines to finish and manually trigger deployment to either `dev-ssi` or `prod-ssi(vault)` clusters.
 
 ## Values
 
-- 
GitLab