This policy outlines the types of data that you can export from an Apollo Hub and import to other Apollo Hubs.
The settings for your Apollo Hub are core to its security, compliance, and operational health. You are unable to export fields that are configured in the Settings & Configuration page in Apollo and import them to another Hub.
Hub settings must be set up by default through Apollo services, or by an administrator on Target Hub initialization. This will ensure that Target Hub administrators can view and understand what settings will not tampered with by the import process.
You cannot export or import role grants for resources, changes to resource ownership, or changes to membership of a Team or Group. Permissions for a Target Hub must be set up from that Hub.
The following items will be exported without settings or permissions. After importing the Bundle, you will need to configure these missing settings from the Target Hub.
You can export and import resources that non-administrator users create, modify, or interact with on a regular basis. This includes new Product Releases, Products, and so forth.
You can export and import Apollo-managed K8s Namespaces on an Environment. Note that if you are exporting a K8s Namespace with the privileged feature enabled, it will be imported as a regular, non-privileged K8s Namespace. After import, you will be able to open a Change Request to mark the imported K8s Namespace as privileged again. This ensures that any privileged K8s Namespaces have been approved on the Hub in which they are running, even if they were imported from another Hub.
Release Channels are not a resource that can be exported on their own, but they can be exported and imported as part of the metadata of a Product Release. The section below will discuss exporting and importing Release Channels in the context of a Product Release, and what happens to Release Channels that are in the metadata of that specific Product Release.
Each Release Channel can be configured to be exportable or not as part of Product Release metadata. The configuration is per Release Channel and can be found under Hub Settings > Release Channels. A Release Channel that is not exportable can still be used as a resource selector in the Export Pipeline configuration, but the exported Product Releases will not include the Release Channel.
When importing a Product Release Apollo will only import the following Release Channels automatically: DEV, RELEASE_CANDIDATE, RELEASE, STABLE, STABLE_2. For all other Release Channels, you must create the Release Channel manually on the Target Hub before importing Product Releases. Furthermore, the Product Release must pass any Release Channel requirements before being promoted to the Release Channel.