Managing DataStage assets
Assets in DataStage® include jobs, flows, components, connections, and parameter sets.
You can use the asset relationship viewer to see how assets use each other. You can also group related assets in folders.
Viewing asset relationships
Use the asset relationship viewer to see which assets use each other. Under the Assets tab, select the overflow menu for an asset and click Show relationships to open the viewer. View an asset's dependencies under Uses. View other assets for which the selected asset is a dependency under Is used by.
When you select multiple assets and click Open, only the first asset opens in a separate tab until you enable popups in your browser.
Grouping assets in folders
You can enable folder support under the Manage tab of your project. View and create folders and subfolders under the Assets tab. Move assets of supported types into folders by clicking Move to folder under an asset's overflow menu.
Git-based version control
Manage changes to your assets by syncing your project with a Git repository.
cpdctl dsjob git-configure {--project PROJECT | --project-id PROJID} [--git-enable] [--git-url URL] [--git-owner OWNER] [--git-token TOKEN] [--git-org ORG] [--git-email EMAIL] [--git-provider GITPROVIDER] [--git-branch GITBRANCH] [--git-folder GITFOLDER]| Attribute | Description |
|---|---|
| project | It is the name of the project. Specify it, when project-id is not
specified. |
| project-id | It is the ID of the project. Specify it, when project is not
specified. |
| git-enable | It allows the project to be Git enabled and starts tracking resource changes. |
| git-url | It is the Git repository URL, for example: https://github.company.com/username/git-dsjob.git |
| git-owner | It is the owner of the Git repository, for example username. This field is
optional. |
| git-token | It is the token, which is used for authentication. This field is encrypted when stored. |
| git-org | It is the Git organization. This field is optional. |
| git-provider | It integrates to a specific provider. It must be git or
gitlab. |
| git-branch | It is a default branch, which is used for Git operations. |
| git-folder | It is a folder to which a project is committed or fetched from. This field is optional. |
You can enable Git integration at the project level from the UI. Under the DataStage section of the Manage tab of your project. After you enable Git integration and select your repository and branch, click Sync to commit changes to the repository or clone them into your project. You can select specific changes to commit or clone without syncing all changes.
You can also commit or clone changes at the asset level. Find your asset under the Assets tab of your project and select the overflow menu. Click Git commit to update the asset in the repository or click Git clone to update the asset in your project. Both Git commit and Git clone options open the Git status page for the selected flow. Click Git status to view all differences between assets in your project and assets in the repository.
- git-commit
-
It allows CPD project resources to push and commit to the Git repository.
Each action is a single signed commit. Commit takes assets from projects and writes to the Git repository under a branch and a folder. Make sure that each project is maintained into a separate folder so the project data is not overlapped. You can commit from the UI. Click the Sync button and choose the Commit changes sync method. You can select assets to commit, or you can commit the entire project.
- git-pull
-
It allows project artifacts from Git repository to be pull and update into CPD Projects.
The
ds-migrationimport service verifies the git pull. You can control which assets can be replaced or skipped when promoting to higher environment. You can pull from the UI. Click the Sync button and choose the Clone from GitHub sync method. You can select assets to pull, or you can pull the entire project from the repository.
- git-status
-
It provides status on resource to identify the differences between the CPD Project and the Git repository.
Git integration provides platform specific computations to determine whether the resource in Git repository is the same as the resource in Cloud Pak project.