After deploying the code from Dev to Test and DB and files from Live to Test, our pages are rendering properly without enabling the custom modules. Is this expected behavior?

[#1]

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]

[chrisnovak]

It is difficult to understand your setup. However, the Pantheon workflow is a standard process for development: Whatever you are doing to Test to change it from the mirror of Live to the next version is your release process, and you will do the same to upgrade Live to the next version.

If the same code is running on Test and Live, then when you put the Live database on Test, both Live and Test environments will be identical. Then, you take the code from Dev and apply it to the Test environment, mimicking the same process you will follow when upgrading the code in the Live environment. If you are replacing the database on Test with the Live database, how would you get duplicate entries in the database?

If you do have an issue with the database being "wrong" when upgrading, then you need to either create code or manual steps to fix the data. One way to automate is to write SQL statements using Drupal's hook_update_N function. This idea and others are part of the configuration management section on that Pantheon workflow document.