Cloning script packages

You can create a script package based on a copy of an existing script package. You can then modify the cloned script package as needed.

Before you begin

You must be assigned the Create new catalog content role or the Workload resources administration role with Full permissions to complete this task. Before cloning an existing script package to create a new one, verify if any previously created script packages in the catalog already meet your needs.

Script packages can contain one or more license agreements that you must accept before you can clone the script package. Review the script package that you intend to clone, and ensure that you accept all license agreements before you attempt to clone the script package. For more information, see the related links.

Important: If, while modifying your cloned script package, you choose to upload a different compressed file than what was copied from the original script package, ensure that any scripts in the new compressed file were created using a text editor that does not introduce control characters. Control characters can cause the scripts to become unusable.
Restriction: Be aware of the following limitations regarding the compressed file that you are uploading:
  • On some web browsers, there is a 2GB limitation on the size of files that can be uploaded. If your compressed file is greater than 2GB in size, you might need to use a different browser that supports uploading larger files, or you should use the command line interface method to upload this file.
  • If your compressed file is packaged in .zip format, the file size must be less than 4GB.
  • For compressed files larger than 4GB, you must package the file in .tgz (.tar.gz) format, and use the command line interface method to upload the file.

For information about uploading a compressed file to a script package using the command line interface, see the related links.

About this task

You can clone an existing script package to create a new script package, configure parameters as needed, and then add your new script package to the catalog, where it will be available for later inclusion in virtual system patterns.
Multisystem environment considerations
  • If you are cloning script packages in a multisystem environment, the operation takes place only on the local system.
  • For information about the fields on the Script Packages page, see Fields on the Script Packages page.

Procedure

  1. Click Catalog > Script Packages. The Script Packages page displays the list of script packages that are currently available. The list is displayed in a table format, providing some basic details about each script package.
  2. Select the script package to be cloned and click the Clone icon in the toolbar.
  3. In the Name field, type a unique name and optional version for the cloned script package and click OK.
    Be sure to use only alphanumeric characters in the name (avoid using any special characters). This name is used as the identifier for the cloned script package that you are adding to the catalog.
    Restriction: Multiple versions of the same script package are not supported for use with classic virtual system patterns.
  4. Click OK.
    The cloned script package is created and initially populated with the same configuration values as the original script package. The name of the cloned script package is displayed in the list of available script packages, and the detailed information is displayed in the pane.
  5. Optional: In the Description field, modify the text description to help identify the cloned script package, in particular indicating what is different from the original script package.
  6. Configure the cloned script package by modifying the information in the fields on the Script Packages pane as needed.
    See the related links for details about how to configure the fields on this page.

    You might choose to first upload a different compressed file that contains your main executable file and associated artifacts. If your compressed file includes a cbscript.json object file, many of these configuration fields will be automatically updated when you upload the compressed file. You can modify these fields after completing the upload as needed. For more information about the cbscript.json object file, see the related links.

    Whether you use the same compressed file from the original script package or you upload a different compressed file, there might be one or more license agreements in these files that become part of the cloned script package. You must accept all license agreements in the cloned script package before you can deploy a virtual system pattern with the script package. For more information about license agreements in script packages, see the related links.

  7. When you complete the configuration for the cloned script package, the script package is saved in the catalog.

What to do next

You can now associate this script package with a virtual system pattern. For more information about working with virtual system patterns, see the Related information section.