Skip to main content

Guidelines for Making VDB Changes During Development

Currently, developers are making changes to the common VDB, and if the changes are incorrect, it causes downtime across all teams by bringing down the VDB. The following actions aim to improve the stability of development environments.

Available DSIS Deployments for DWP​

  • dsdata and dsdsedm
  • dsdatadwp and dsdsedmdwp (currently in use)

Actions to Avoid Issues in Dev Environments Caused by VDB Changes​

  • VDB deployment with the DSDWP client from feature branches will no longer be allowed.
  • All developers must follow the instructions below when making VDB changes.

Steps for Making VDB Changes​

  1. Create a Copy of the VDB for Any Changes

    • Rename the VDB and model to avoid conflicts.

  2. API Test the VDB Changes

    • Use tools like Postman to verify that the VDB returns expected results without issues.

  3. Test the Service

    • Update the deployment to point to dsdsedm/dsdata for testing.

  4. Optional: Test Changes from the UI Using a Feature Branch

    • In dwp-spec, create a feature branch with the suffix -deliver:
      • application_name: DSDWP_PI
      • dsdata_url: dsdata
      • dsdsedm_url: dsdsedm
    • In dwp-config, create the same feature branch with the suffix -deliver:
      • Deploy the feature branch.

  5. Merge VDB Changes

    • Merge the VDB changes into Dev Int to deploy the VDB with the DSDWP client for QA validation on dsdsedmdwp/dsdatadwp.
Connecting...