cloud.connections_enabled.
A connection is a named record of one cloud account on your control plane. It holds non-secret settings (region, account or tenancy ID, compartment, role ARN, subscription ID) and a reference to a credential. It never holds the credential. Everything stays on your control plane: nothing is sent to a hosted service.
What works today
The real read-only checks for Oracle, AWS and Azure need each cloud’s client library. Adding those dependencies is a separate decision, so the providers are registered as not implemented until then.
Turn it on
APP_CLOUD_CONNECTIONS_ENABLED only seeds the default. A stored value wins and applies without a restart.
Use it
Health classes
test returns one class and a fixed short reason. Provider output is never passed through.
API
GET, POST on /api/v1/settings/cloud-connections, PUT, DELETE on /api/v1/settings/cloud-connections/{name} and POST on /api/v1/settings/cloud-connections/{name}/test. While the setting is off every route answers 403 with a message naming it.