​
GraphQL Configuration Guide for Tensor One

When configuring your environment using GraphQL, it’s important to provide all required arguments to ensure successful deployment and operation of Clusters or Templates.

​
Required Configuration Arguments

Below is a list of key configuration fields commonly used in GraphQL mutations for launching resources in Tensor One.

​
containerDiskInGb

  • Description: Sets the disk size allocated for the container (in GB)
  • Use Case: Stores the OS, software, and temporary data
  • Type: Integer
  • Example:
containerDiskInGb: 10

​
dockerArgs

  • Description: Custom command to run when the container starts. Overrides the default CMD or ENTRYPOINT.
  • Use Case: Keep the container running, run startup scripts, or install dependencies
  • Type: String
  • Example:
dockerArgs: "sleep infinity"

​
env

  • Description: Environment variables as key-value pairs
  • Use Case: Set runtime configs, secrets, file paths, or external URLs
  • Type: Dictionary or Object
  • Example:
env: {
  "DATABASE_URL": "postgres://user:password@localhost/dbname"
}

​
imageName

  • Description: The Docker image to use (optionally include tag)
  • Use Case: Define the base runtime environment
  • Type: String
  • Example:
imageName: "nginx:latest"

​
name

  • Description: A unique name to identify the container or Template
  • Use Case: Useful for reference in logs, API calls, and dashboards
  • Type: String
  • Example:
name: "my-app-container"

​
volumeInGb

  • Description: Size (in GB) of the persistent storage volume
  • Use Case: Stores data across restarts or redeployments
  • Type: Integer
  • Example:
volumeInGb: 5

​
Final Notes

  • All required fields must be included in your GraphQL mutation to avoid deployment errors.
  • Some optional fields may also be available depending on your use case, such as:
    • volumeMountPath
    • readme
    • ports
Explore the Templates API Reference or Managing Templates to learn more about optional configurations and advanced usage.