Oracle Cloud Infrastructure Documentation

Importing a Runbook Version

Import a version of the runbook along with its associated resources and dependencies in Fleet Application Management.

  • Importing a runbook version consists of the following pages:

    On the Runbook versions list page, select Import runbook version. If you need help finding the runbook versions list page, see Listing Runbook's Versions.

    Run each of the following workflows in order. You can return to a previous page by selecting Previous.

    1. Select runbook

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

    Enter the following information:

    • Select one of the following options for the runbook version:
      • Increment version: Turn on the toggle to increment the runbook version number.
      • Retain the source version: Turn on the toggle to keep the runbook version same as version number from the source.
      • Replace: Turn on the toggle to replace an existing runbook version and its version number with the source version.
    • 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.

    2. Validate dependencies

    During the validation process, Fleet Application Management checks for required dependencies such as products, lifecycle operations, and catalog items and proceeds as follows:

    • If dependencies do 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 (for example, Terraform package or configuration file for provisioning runbooks) are needed, select Create new and then map them during the import process. See Creating a Private Catalog Item.

    Select Import to begin the process.

    The runbook version import process starts and Fleet Application Management opens the import status screen. After the import process is complete, a new runbook version is listed in the Runbook versions 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.

    Handling Conflicts During Import

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

    • Runbook version conflict: If a runbook with the same version exists in the target tenancy or compartment, the import fails. To resolve this, choose a different version (for example, increment the version).
    • Dependency conflicts:
      • If required dependencies (for example, catalog items) do not exist in the target, Fleet Application Management creates them automatically during the import.
      • If dependencies exist but are incompatible, the import fails, and you receive an error message. To resolve this, you can manually map to different resources or create new ones. See 2. Validate dependencies.

  • This task can't be performed using the CLI.

    For a complete list of flags and variable options for Fleet Application Management CLI commands, see the CLI for Fleet Application Management.

  • This task can't be performed using the API.