[airavata] branch AIRAVATA-3326-improved-database-migration-script-creation updated: AIRAVATA-3326 docs update

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

machristie pushed a commit to branch AIRAVATA-3326-improved-database-migration-script-creation
in repository https://gitbox.apache.org/repos/asf/airavata.git


The following commit(s) were added to refs/heads/AIRAVATA-3326-improved-database-migration-script-creation by this push:
     new f51fc4e  AIRAVATA-3326 docs update
f51fc4e is described below

commit f51fc4e4cd2a9d3316b47e806296c0e1b6c76833
Author: Marcus Christie <ma...@iu.edu>
AuthorDate: Tue Jun 23 11:16:31 2020 -0400

    AIRAVATA-3326 docs update
---
 modules/registry/registry-core/README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/modules/registry/registry-core/README.md b/modules/registry/registry-core/README.md
index 8f5cf35..d1fa5a1 100644
--- a/modules/registry/registry-core/README.md
+++ b/modules/registry/registry-core/README.md
@@ -6,6 +6,9 @@ scripts, both the scripts that define the entire schema for brand new databases
 older schema to the new schema (referred to from here on as the _migration
 script_). These instructions show you how to create these scripts.
 
+Before using these steps, be sure to review the **Known Issues** section later
+on. Notably, any removals from the schema will have to be manually managed.
+
 1. First, start by adding or updating the Entity class, for example, by adding a
    new field.