Control cost by putting unused environments to sleep
Using an isolated, production-like environment is a great way to improve the development pace. However, cloud resources are expensive. With Velocity, you can verify that environments will be used only when needed.
You can put an environment to sleep and store its data while it is not in use. Afterward, you can wake up the environment when you wish to continue working on it.
In addition, Velocity provides automated processes that put environments to sleep based on a predefined TTL (Time to Live). TTL ensures that the resources will not be used if the user forgets to put the environment to sleep.
Moreover, Velocity also provides a termination policy that destroys the environment with its data, based on a TTD (Time to Destroy).
NOTE: Velocity monitors the usage of your environment and avoids putting the environment to sleep or destroying it if it in use.
Putting the environment to sleep
To put an environment to sleep, run the following command from the command line:
veloctl env sleep
This command shuts down the environment, but preserves its data for later use.
Environments may automatically get to sleep depending on the default definitions of the account.
Example - to put 'johns-feature' to sleep, enter:
veloctl env sleep johns-feature
Waking up an environment
To wake up your currently set environment, run the following command from the command line:
veloctl env wakeup
This command wakes up the environment and allows you access to the preserved data, so you can resume development from the same state it was in when it was put to sleep.
Example: to resume work on johns-feature after putting it to sleep, enter: