vidakovic commented on code in PR #2689:
URL: https://github.com/apache/fineract/pull/2689#discussion_r1001797101
##########
fineract-doc/src/docs/en/chapters/architecture/modules.adoc:
##########
@@ -63,6 +63,15 @@ If database migrations are needed as part of your
customizations then you can ad
include::{diagramsdir}/custom-db-migration-folder-structure.puml[]
----
+And here an example migration script:
+
+[source,xml]
+----
+include::{rootdir}/custom/acme/note/starter/src/main/resources/db/custom-changelog/0001_acme_note_initial.xml[lines=22..]
+----
+
+IMPORTANT: Please make sure your `changeSet` tag has the attribute `context`
set to `tenant_db`. That makes sure your changes will be applied to the tenant
database (read: main database and not the tenant store database). In theory you
could also target the tenant configuration database, but it's not recommended
to do that.
Review Comment:
Well, from my perspective that tenant configuration DB should disappear
anyway, but that's a topic for another day. In general I agree (they shouldn't
touch that one), but then in the end: they own the system they are running
on... so there's not much that we can do here if they really wanted to; which
makes this pointless I guess.
As for "level up": I guess you mean in fineract-provider? Sure, we can set
it there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
