Example for release type - Catalog-to-catalog

Edit online

This sample shows how to create a catalog-to-catalog release.

What are the requirements?

Table 1. Requirements for creating a catalog-to-catalog release
Requirement Description
User Db2 CD administrator or Db2 CD operator
Purpose To deploy objects across environments with the manifest and path.
Prerequisites Before creating a release, you must create the following in the User Interface (UI):
  • A path, for example, Blue. The blue path must have environment E2 (source node) in development, environments E3, E4, and E5 (target nodes) in QA, and environment E6 (target node) in production. For more information, refer to Creating a path.
  • A catalog manifest with the required filters. For example, M1.
    • Use the Evaluate option in the manifest by selecting the Evaluation environment as E2. This evaluation shows the list of objects that you will be deploying in a release. For more information, refer to Creating a manifests.
    • Change the status to Active.
Deployment type Catalog-to-catalog

Description

In this example, you will see how are catalog-to-catalog release RD1 is created for the manifest M1 and the Blue path as shown in the below workflow.

How to create?

  1. Go to Create release API.
  2. Click Try it out and provide the required values to create a release.
    Table 2. Parameters for a catalog-to-catalog release
    Parameter User Input
    releaseType

    (query)

    		 C
    requestBody

    (body)

    		 
    {
  "manifestName": "M1",
  "pathName": "Blue",
  "releaseDesc": "This is a sample catalog release for blue path.",
  "releaseName": "RD1"
}
    Click Execute.
    Response
    {
"returnCode": "SUCCESS",
"messages": [null],
"result": {
"createdTS": "2025-02-05-06.35.07.583379-05:00",
"createdBy": "CSMVDQE",
"createdInRelease": "1.2.1",
"updatedTS": "2025-02-05-06.35.07.583379-05:00",
"updatedBy": null,
"updatedInRelease": null,
"releaseUUID": "ff8482e3-a6d7-439b-8e8c-40b976f168f2",
 "releaseName": "RD1",
"releaseStatus": "A",
"releaseDesc": "release demo",
"consolidatedReleaseUUID": null,
"manifestUUID": "421c045b-f5f1-48d9-971c-934291a455d6",
"manifestName": "M1",
"pathUUID": "a9672b3d-4ca9-4fa8-a242-13cda6e331d1",
"pathName": "Blue",
"initiatingEnvUUID": null
 }
}

What to do next?

After creating a catalog-to-catalog release, you can deploy the Db2 objects from one node to another in the selected path. For more information, refer to Example – Catalog-to-catalog deployment.