Docs

Config Export/Import

What this screen is for

Config Export/Import moves a Fenwave configuration between installations. You can export everything, or select what to include, and import a bundle into another install.

Use it to stand up a second environment from a known-good configuration, to keep a copy before a risky change, or to hand a working setup to another team.

Before you start

To do this You need
Export a configuration platform-settings.config.export
Import one platform-settings.config.import

An import replaces configuration

Importing is not a merge in the harmless sense — it writes the bundle’s configuration into the target install, overwriting what is there. Export the target’s current configuration first. That export is your only way back.

Opening it

  1. Settings in the sidebar.
  2. Config Export/Import.

Direct URL: /platform-settings/config-export

The interface

📸 Screenshot Placeholder: The Config Export/Import page. Mark: (1) the export action, (2) the selective-export dialog, (3) the import action.

# Control What it does When you’d use it
1 Export Produces a bundle of the current configuration Backups, migrations
2 Selective export Choose which parts to include Moving one area rather than everything
3 Import Applies a bundle to this install Setting up or restoring

Prefer selective export when you know what you are moving. A full bundle carries infrastructure registrations that may be meaningless — or actively wrong — on the target.

Walkthroughs

Export the configuration

Requires platform-settings.config.export.

  1. Settings › Config Export/Import.
  2. Choose a full or selective export. For selective, pick the areas.
  3. Download the bundle and store it where you keep operational artefacts. It describes your infrastructure — treat it accordingly.

Import a configuration

Requires platform-settings.config.import.

  1. Export the target install’s current configuration first. Do not skip this; it is the only rollback you get.
  2. Choose the bundle and import it.
  3. Work through Infrastructure and validate every cloud credential and cluster. An imported registration is a record, not a proven connection — expect statuses to read Pending.
  4. Check People & Access: roles and policies may reference clusters and environments that do not exist here under those names.
  5. Spot-check with Access Explorer before letting anyone use the install.

Scenario

Standing up a second Fenwave install for a new region, from a working one.

  1. On the source install, take a selective export. Include the roles, policies and project structure — the parts that encode how you work.
  2. Consider excluding the infrastructure registrations. The new region has different clusters and different credentials, and importing the old ones creates registrations that will only ever read Invalid.
  3. On the target, export its current configuration first, even if it looks empty. An install that looks empty and is not will bite you here.
  4. Import the bundle.
  5. Register this region’s cloud account and clusters fresh, and validate them.
  6. Create the environments on those clusters.
  7. Open the imported policies. They were scoped to the source clusters and environments, which do not exist here — re-scope them to the new ones. A policy scoped to a missing cluster does not fail loudly; it simply never matches.
  8. Verify a representative user with Access Explorer.

Step 7 is where this goes wrong when it goes wrong. Roles and policies import cleanly and look correct, while granting nothing at all.

When it doesn’t work

Symptom Cause How to check Fix
Import succeeded, nobody can do anything Policies are scoped to clusters and environments that do not exist here The policy statements Re-scope to this install’s clusters and environments
Clusters imported but all read Pending or Invalid Registrations were copied; credentials were not proven here Clusters Validate each one; re-enter credentials where needed
Import overwrote something you wanted Import replaces configuration Your pre-import export Re-import the export you took first — which is why you take it
Export action absent Missing platform-settings.config.export Access Explorer Ask for a role granting it
Import rejected The bundle is malformed or from an incompatible version The error on the page Re-export from the source

Next