Skip to main content
Cloud adapter configuration describes settings shared by an installation. Service adapter configuration describes one specific service adapter. Use these scopes to keep installation concerns separate from a service’s backend choices.

​
Cloud adapter configuration

Prepare the installation-wide decisions: which clouds you adapt from and to, deployment location, connectivity, shared state and operational requirements. These settings should not have to be repeated independently for every service adapter.

​
Service adapter configuration

For each service, identify the origin API, chosen backend, required backend resources and credentials, and the endpoint your application will use. Consult that mapping’s reference for service-specific requirements. Cloud Adapter combines both scopes in one reviewable configuration. Use the fields documented for your installed release and selected service mappings.

​
Two setup paths

File-based setup will accept the complete installation configuration. Use it when you need reviewable, repeatable input. Guided setup asks the same questions in a terminal UI and generates the configuration. You can select options, validate answers, revisit earlier choices and review the result before proceeding. It does not require an AI agent. Both paths must produce the same validated configuration. Saving a file and applying it are different actions; a saved configuration is not evidence that resources have been provisioned.

​
Treat changes as transitions

Compare a proposed configuration with the installed one. A syntactically valid file may request an unsafe or unsupported transition, particularly when persistent data is involved. The upgrade workflow checks compatibility, performs supported migrations and coordinates rolling restarts. Editing a file alone is not an upgrade procedure.

​
Handle secrets separately

Keep a redacted configuration suitable for review. Do not commit secret values, signed requests or backend credentials. Record which identity owns each backend resource and the permissions needed for normal operation versus provisioning. Use secret references supported by your installed release. Keep secret values out of configuration files, reviews and support transcripts.