Learn about the ways to promote assets from a project to a deployment space and additional requirements for promoting specific asset types.
For a list of assets that can be promoted from a project to a deployment space, refer to Adding assets to a deployment space.
You can promote assets to a deployment space in the following ways:
- To promote an asset to a deployment space: in the project Assets page of your project, from the options menu for the asset (
), choose Promote to space.
When you are promoting assets, you can:
- Choose an existing space or create a new one
- Add tags to help identify the promoted asset
- Choose dependent assets to promote them at the same time
Notes:
- Promoting assets and their dependencies from a project to a space by using the Watson Studio user interface is the recommended method for guaranteeing that the promotion flow results in a complete asset definition. For example, relying on the Watson Data API to manage the promotion flow of an asset, together with its dependencies, can result in the promoted asset being inaccessible from the space.
- Promoting assets from default Git-based projects is currently not supported.
- Depending on your configuration and the type of asset being promoted, large asset attachments, typically more than 2 GB, can cause the promotion action to timeout.
For additional information on promoting specific asset types, refer to:
Promoting connections and connected data
When you promote a connection that uses personal credentials or Cloud Pak for Data authentication to a deployment space, the credentials are not promoted. You must provide the credentials information again or allow Cloud Pak for Data authentication
Because Storage Volume connections support only personal credentials, to be able to use this type of asset after it is promoted to a space, you must provide the credentials again.
Some types of connections allow for using your personal
platform credentials. If you promote a connection or connected data that uses your personal platform credentials, tick the Use my platform login credentials checkbox.
Although you can promote any kind of data connection to
a space, where you can use the connection is governed by factors such as model and deployment type. For example, you can access any of the connected data by using a script, but in batch deployments you are limited to particular types of data,
as listed in Creating a batch deployment.
Promoting models
When you promote a model to a space:
- Components that are required for a successful deployment, such as a custom software specification, model definition, or pipeline definition are automatically promoted as well.
- The data assets that were used to train the model are not promoted with it. Information on data assets used to train the model is included in model metadata.
Promoting notebooks and scripts
-
If you created a job for a notebook and you selected Log & updated version as the job run result output, the notebook cannot be promoted to a deployment space.
-
If you are working in a notebook that you created prior to IBM Cloud Pak for Data 4.0, and you want to promote this notebook to a deployment space, perform the following steps to enble promoting it:
- Save a new version of the notebook.
- Select the newly created version.
- Select either Log & notebook or Log only as the job run result output under Advanced configuration.
- Rerun the job.
Now you can promote it manually from the project Assets page or programmatically by using CPDCTL commands.
-
If you want to promote a notebook programmatically, use CPDCTL commands to move the notebook or script to a deployment space. To learn how to use CPDCTL to move notebooks or scripts to spaces, refer to CPDCTL code samples. For the reference guide, refer to CPDCTL command reference.
Learn more
- For details on adding data assets to a space, refer to Adding data assets to a deployment space.
- For details on importing models to a space, refer to Importing models into Watson Machine Learning.
Parent topic: Assets in deployment spaces