Assets in deployment spaces

Learn about various ways of adding and promoting assets to a space. Find the list of asset types that you can add to a space.

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.

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.

For more information, see:

Asset types that you can directly add to a space
Asset types that are created in projects and can be transferred into a space
Asset types that can be added to a space only as a dependency

For more information about working with space assets, see:

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

If your asset is located in a standard Watson 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.

Alternatively, you can export the project and then import it into the deployment space. For more information, see:

If you export the whole project, any matching custom environments are exported as well.

If your use case requires it, you can create a code package from some of the assets in your project by using cpdcli or cpdctl and then importing manually into the space.

Transferring assets from a deprecated Git-based project

The available scenarios are the same as the ones that apply to transferring assets from a standard Watson Studio project.

Note:

Transferring assets from a standard Git-based project

Before you move assets to a deployment space, you must synchronize your changes with the Git repository. If your asset depends on any other assets, like custom environments, you must synchronize those assets as well. To transfer your assets from a standard Git-based project, export the project and then import it into the deployment space. For more information, see:

If you export the whole project, any matching custom environments are exported as well.

If your specific use case requires it, you can also create a code package from some of the assets in your project by using cpdcli or cpdctl and then import it manually into the space.

Note: When you work with a Git-based project, Notebooks, Scripts, and Shiny Apps are represented as files within your Git repository. When you import your Git archive file into a deployment space, all of these file types are accessible within the Code Package asset that is created as part of the import.

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

Hardware Specification
Package Extension
Software Specification
Watson Machine Learning Experiment
Watson Machine Learning Model Definition

Learn more

Parent topic: Deployment spaces