Assets in deployment spaces

Last updated: Nov 21, 2024

Learn about various asset types that you can use in your deployment spaces and the ways of adding and promoting these assets to a space.

The way to add an asset to a space depends on the asset type. You can add some assets directly to a space. For example, you can add a model that was created outside of Cloud Pak for Data to your deployment space. Other asset types originate in a project and must be transferred from a project to a space. The third class includes asset types that you can add to a space only as a dependency of another asset. These asset types do not display in the Assets tab in the UI.

Note these considerations for importing assets into a space:

Upon import, some assets are automatically assigned a version number, starting with version 1. This version numbering prevents overwriting existing assets if you import their updated versions later.
Assets or references that are required to run jobs in the space must be part of the import package, or must be added separately. If you don't add these supporting assets or references, jobs fail.

Asset types that you can directly add to a space

Connection
Data asset (from a connection or an uploaded file)
Model

For more information, see:

For data assets and connections: Adding data assets to a deployment space
For models: Importing models into a deployment space

Assets types that are created in projects and can be transferred into a space

Connection
Data Refinery flow
DataStage Build stage
DataStage Custom stage
DataStage Data definition
DataStage flow
DataStage Function library
DataStage Java Class library
DataStage Match specification
DataStage Operational Decision Manager component
DataStage subflow
DataStage Schema library
DataStage Standardization rule
DataStage Wrapped stage
Environment
Function
Job
Parameter set
Pipeline
Script

See Transferring assets to your deployment space.

Asset types that can be added to a space only as a dependency

Hardware Specification
Package Extension
Software Specification
watsonx.ai Runtime Experiment
watsonx.ai Runtime Model Definition

Transferring assets to your deployment space

If your asset is located in a standard watsonx.ai Studio project, you can transfer the asset to the deployment space by promoting it.

For more information, see Promoting assets to a deployment space.

Note:

If the asset that you want to transfer to a deployment space is a notebook that uses a custom environment, you must transfer the environment as well. In some cases, you must transfer the environment as a separate step. You can locate your custom environment in the Manage tab and then promote it.

You can also import whole spaces and projects into a deployment space. For more information, see:

Learn more

For more information about working with space assets, see:

Parent topic: Deployment spaces