Skip to main content
File-based setup supports repeatable installations and configuration changes that can be reviewed before they are applied. The file describes the installation completely enough for the same setup workflow used by guided configuration.

​
Prepare the decisions

Collect the origin and target cloud direction, the service mappings your workload requires, the deployment location, backend resources, connectivity and identities. Keep shared cloud adapter settings separate from each service adapter’s decisions. Record the source of each value and who may change it. A backend identifier copied from a development environment should not be mistaken for a production resource.

​
Review before applying

Review configuration changes alongside the installed version and current settings. Check changes to endpoints, credentials, resource identities and persistent storage especially carefully. Use version control for non-secret configuration and review notes. Do not put secret values, signed URLs or credential files in commits. Store credentials through the configuration’s supported secret-reference fields.

​
Preserve the installed configuration

Retain the configuration actually used for an installation, not only the latest edited file. It is the starting point for compatibility checks and a useful input to debugging. A desired file is not a deployment record. The upgrade workflow validates the transition and reports what was applied. Modifying a remote or local file does not immediately change running adapters. For first-time setup, guided configuration generates the same configuration rather than a separate installation format.