Importing a Runbook

The Select runbook page is where you provide the runbook package location information for importing it.

Enter the following information:

• Name: Enter a name for the imported runbook. You can choose a different name if a runbook with the same name exists.
• Import in Compartment: Select the compartment to import the runbook.
• Retain the source version: To keep the original version number of the runbook from the source, turn on the switch.
• Select exported package: Select one of the following options to indicate where you can access the runbook package:
  • Object storage: Select the bucket compartment and Object Storage bucket that contains the runbook ZIP file. Then, select the specific runbook bundle (ZIP) from the list.
  • URL: Enter a pre-authenticated request (PAR) URL link for the runbook bundle and enter the runbook bundle (ZIP) URL link in File url.
• Destination bucket: Select the bucket compartment, Object Storage bucket, and specify the directory where you plan to store the dependencies after the import.

Select Next to continue.

During the validation process, Fleet Application Management checks for required dependencies such as products, lifecycle operations, and catalog items. The following scenarios can occur:

• If a required dependency does not exist in the target tenancy or compartment, Fleet Application Management automatically creates it using the exported information.
• If the dependency exists in the target but you want to map it to a different resource, you can manually specify the mapping. For example, if a catalog item of type Terraform, based on an external repository or file upload, is present in the exported runbook, you must provide the OCID of an existing Terraform catalog item from the target tenancy.
• If a new catalog item, such as a Terraform package or configuration file needed for a provisioning runbook, is required, select Create new and map it during the import process. See Creating a Private Catalog Item.

Select Import to begin the process.

The runbook import process starts and Fleet Application Management opens the import status screen. After the import process is complete, a new runbook is listed in the Runbooks list page.

You can also navigate to the import status screen from the Runbooks list page by selecting Actions and then selecting View import and export status to ensure the import completes successfully.

Fleet Application Management might report conflicts during the import process that you need to address:

• Runbook name conflict: If a runbook with the same name already exists in the target tenancy or compartment, the import fails. To resolve this, provide a different name for the imported runbook.
• Dependency conflicts:
  • If required dependencies (such as catalog items) are missing in the target, Fleet Application Management creates them automatically during the import.
  • If existing dependencies are incompatible, the import fails, and you receive an error message. To resolve this issue, you can either manually map to different resources or create new dependencies. See 2. Validate dependencies.