I am following the pantheon doc "https://pantheon.io/docs/pantheon-workflow/" for deployment of code from dev to Test and DB and content files from Live to Test.
On Dev-env of the portal, we have following modules …..
-fhir_responsive theme with apigee responsive base theme
-fhir_blocks which includes all the blocks of the sites
-fhir_custom which include other fratures
-fhir_install which includes some DB entries to enable of main menu.
On Live-env of the same portal we have third party licensed theme installed which is configured and is almost similar to our custom code(On Dev-portal).
Our requirement is to merge our custom code which is deployed on "dev-env" of a portal, with the Database of live of environment(as it includes all user account details). As per document, we are merging by moving dev code to test env and live db to test environment.
Doing so would create duplicate entries in db as our custom code would also create entries when we enable our custom modules.
Please suggest how to segregate db entries in such scenarios.[we require only user account details from live db]
LinkedIn
Twitter
