From afb9527871a0160b24e9a62698c85e29d8496983 Mon Sep 17 00:00:00 2001
From: Brett Meehan <bmeehan@atlassian.com>
Date: Mon, 16 Dec 2019 14:25:24 +1100
Subject: [PATCH] ITOPSENG-333 put comment in code to explain the need for
 skipping db_create

---
 roles/database_init/tasks/main.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/roles/database_init/tasks/main.yml b/roles/database_init/tasks/main.yml
index 070b33d..e065a0a 100644
--- a/roles/database_init/tasks/main.yml
+++ b/roles/database_init/tasks/main.yml
@@ -31,6 +31,7 @@
         objs: "{{ atl_jdbc_user }}"
         type: group
 
+# RDS does not allow changing the collation on an existing DB, it only allows collation change on creation of db. If the db already exists, we need the “create new application database” task to be skipped, idempotence can not be relied upon as we cant be certain the collation of the existing db
     - name: Create new application database
       postgresql_db:
         login_host: "{{ atl_db_host }}"