How to do Content promotion when different Developer Portal Environments link to Different EDGE organizations?

Not applicable

Our Developer Portal Dev and Test portals point to Organization A
Our Developer Portal Live portals point to Organization B

Dev and Test have our customizations that are represented in both code and content of those sites.

When we promote code and content from Dev -> Test -> Live , along with desired customizations like UI , things like apps / organization changes also get pushed to Live.

How can we only push desired content changes / Separate Org A to dev and test and Org B to live ?

Solved Solved
0 4 484
1 ACCEPTED SOLUTION

@AlayVakil ,

From long time, It's one of of the most needed & missing feature in out of the box Drupal 7 CMS on which Apigee Developer Portal is built on. There are workarounds & contributed modules to overcome these issues. Please find details regarding same below.

Regarding, Developer Apps / Organization Settings,

  • Developer App details are never stored in Apigee Developer Portal, They are always pulled using Management APIs & Displayed in Developer Portal.
  • Organization settings like which Apigee Edge org developer portal is connected stored in private file system.
    • If you migrated files between your developer portal environments, most likely you will endup seeing same apps & organization settings.
    • To revert, Using drush commands to update each developer portal environment connection settings to Apigee Edge Org.

Regarding, Configuration changes of Developer Portal


  • They are stored in Database along with content.
  • You need to export them into module code format using modules like features
  • Move the exported module code into new environment, enable the module & pull changes.

Regarding, Content changes of Developer Portal


  • It's stored in database
  • Never push database from one environment to other, it will result in data loss. For example, If you override live environment database with dev , All the users & user content created in live environment will be lost.
  • Use module like https://www.drupal.org/project/node_export to export import content.

Hope it helps. Keep us posted if any.

View solution in original post

4 REPLIES 4

things like apps / organization changes also get pushed to Live.

can you elaborate on what you mean by this? what apps? What org changes?

The org setting is completely independent of the code push that you do in the Pantheon dashboard. So I don't understand what you mean by the above.

@AlayVakil ,

From long time, It's one of of the most needed & missing feature in out of the box Drupal 7 CMS on which Apigee Developer Portal is built on. There are workarounds & contributed modules to overcome these issues. Please find details regarding same below.

Regarding, Developer Apps / Organization Settings,

  • Developer App details are never stored in Apigee Developer Portal, They are always pulled using Management APIs & Displayed in Developer Portal.
  • Organization settings like which Apigee Edge org developer portal is connected stored in private file system.
    • If you migrated files between your developer portal environments, most likely you will endup seeing same apps & organization settings.
    • To revert, Using drush commands to update each developer portal environment connection settings to Apigee Edge Org.

Regarding, Configuration changes of Developer Portal


  • They are stored in Database along with content.
  • You need to export them into module code format using modules like features
  • Move the exported module code into new environment, enable the module & pull changes.

Regarding, Content changes of Developer Portal


  • It's stored in database
  • Never push database from one environment to other, it will result in data loss. For example, If you override live environment database with dev , All the users & user content created in live environment will be lost.
  • Use module like https://www.drupal.org/project/node_export to export import content.

Hope it helps. Keep us posted if any.

Thanks @Anil Sagar

That makes it much clearer

Glad it's helpful. Keep us posted moving forward if any.