Skip to main content
The Tensor9 CLI provisions a Cloud Adapter and its supporting resources into a target environment.The Tensor9 CLI provisions a Cloud Adapter and its supporting resources into a target environment.
The provisioned deployment lets the local Tensor9 CLI create and operate the cloud resources that run your adapter. The adapter remains your application’s origin-cloud API surface; the CLI coordinates its placement, identity, networking and lifecycle in the target cloud.

​
When to use it

Use a provisioned deployment when you want repeatable installation, cloud-native networking and an explicit infrastructure lifecycle without hand-assembling every runtime resource.

​
Installation flow

  1. Supply a configuration file, or answer the guided setup questions to generate one.
  2. Review the proposed resources, identities and network paths.
  3. Let the CLI provision the target-cloud resources and start the adapter.
  4. Verify the endpoint with a small request before directing application traffic.
The generated configuration is the durable input to the deployment. Store it with the same review and change controls as infrastructure configuration.

​
Updates and ownership

The local CLI coordinates compatible configuration updates, migrations and rolling restarts. It blocks changes that would require an unsupported live migration, such as changing a backend with no migration plan. You own the provisioned resources, credentials, data and cloud billing; Tensor9 supplies the adapter implementation and orchestration behavior.