CDQ Data Quality as Service

Idea Portal

Add central configuration management and configuration copy/transport functionality

We are implementing a three tier workspace scenario with a development, quality/test and productive environment + a separate "playground/sandbox" environment for WebApp testing. The different work spaces will be connected to our existing applications, which are calling the CDQ APIs e.g. data maintenance workflow application (CDQ QA -> WF Quality / CDQ PROD -> WF Prod),.

Currently, the configuration needs to be setup individually in each workspace and the workspace configurations are only visible in the corresponding workspace. It is not possible to copy/transport configurations between the different workspaces, e.g. after development is ready configured transport/copy into QA workspace for testing (or we did not find it).

A copy function of the configurations between the workspaces (including possibility to adjust the name during the copy process) would certainly reduce manual maintenance effort (compare to data source management which are all maintained in the same spot).

Following features would be required:

  • Display of all configurations from all workspaces

  • Display what workspace and what API/feature is using which configuration, e.g. specific "Data Curation Config" is used in WS xyz- curation

  • Copy/transport feature for selected configurations to another workspace -> Settings made in DEV can be transported to QA / PROD

  • Allow renaming of the configuration during the copy process, e.g. BP_DATA_VAL_QA to BP_DATA_VAL_PROD

  • Configuration name should be unique across all workspaces to avoid unintended overlaps

  • Change history for configuration would help tracking changes

  • Last CHANGE user to be displayed - currently only the creator is shown


Thanks a lot!

  • Alexander Mack
  • Sep 30 2022
  • Future consideration
  • Attach files
  • Onur Dinc commented
    December 23, 2022 08:55
    • Usage of the Conifguration should be displayed: Is it used in an API-Key? Is it used in Data-Monitoring? If so, it should be not possible to delete it, until it has been unassigned