After initial deployment, we ship updates to the application running in your environment. Here’s how that works.Documentation Index
Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
Use this file to discover all available pages before exploring further.
How Updates Work
What Gets Updated
- Application code - New features, bug fixes, performance improvements
- Application infrastructure - If the update requires changes to supporting resources (a new database table, a modified IAM policy), the controller applies those via Terraform in your environment
- Configuration - Updated environment variables, resource limits, or other application settings
What Doesn’t Change Without Notice
- Your infrastructure - We don’t modify your VPC, subnets, or security groups without telling you
- Your permissions - We don’t change the controller’s role or bindings silently
- Your secrets - We never touch secrets you created
Your Control
You always have the option to:- Pause updates - Freeze your deployment at a specific version for as long as needed
- Review changes - See exactly what’s in an update before it’s applied
- Roll back - If an update causes issues, the controller can revert to the previous version
Infrastructure Changes
Occasionally, an update may require changes to supporting infrastructure (e.g., a new S3 bucket, an additional IAM policy). When this happens:- We coordinate with you before making the change
- The controller applies the Terraform changes in your environment
- You can review the Terraform plan before it’s applied
The Update Process
