Deep Cloning a Runbook
Copy a runbook along with all its associated resources and dependencies, not just its structure in Fleet Application Management.
With deep cloning, you can copy the following items:
- The runbook structure
- Associated resources, such as products, lifecycle operations, tasks, and catalog items
- Scripts or files uploaded to Object Storage
- Configuration files and Terraform packages (for provisioning runbooks)
This process ensures that the runbook and all required resources can be migrated or copied between compartments or tenancies.
Use deep cloning when you want to reuse a runbook in a different compartment or tenancy while maintaining all its dependencies.
Key Resources Associated with a Runbook
When you deep clone a runbook, Fleet Application Management copies the following resources:
- Product information: Product name, version, and stack details
- Lifecycle operations: The specific operation the runbook is designed for, such as patching).
- Tasks: Each step in the runbook is a task, including commands or scripts
- Catalog items: Terraform packages and configuration files for provisioning runbooks
- Scripts and files: Files uploaded to Object Storage for use in tasks.
See the following deep cloning topics: