Now that you’ve created your first cloud account, let’s launch a sample blueprint. A blueprint is an offline model of an application stack in a specific cloud provider or Kubernetes cluster. When launched, the blueprint spins up a sandbox, which is an on-demand, time-limited environment deployed to your cloud provider and designed to facilitate any dev/test task. An example scenario includes testing a new build of an application or reproducing bugs on a customer-like environment. Sandboxes are created based on blueprints, which are managed by the Space owner and published to a self service Blueprints Catalog for independent consumption by your Space member. A sandbox
To help get you familiarized with the concept of sandboxes and their capabilities, we’ve set up a Sample space with several pre-defined blueprints you can use. These blueprints are defined to use the first cloud provider you create, which is named either “AWS” or “Azure”.
To launch a Sample sandbox:
- In the top left corner of Torque, click Space and select Sample.
- Click the Sandbox Environments tab on the left.
- Click the blue New Sandbox button.
The Blueprints Catalog is displayed, showing the sample blueprints.
Only published blueprints are displayed. For details, see Publishing Blueprints to the Blueprints Catalog.
- Double-click the blueprint.
Optionally, use the Search by name field to find the required blueprint.
- Enter your Sandbox Name, preferred Duration, and required Parameters.
Each sandbox may require different parameters and artifacts details. These are defined in the blueprint used to launch this sandbox and may include a default value. Parameters defined in the blueprint YAML need to be filled in when launching the sandbox. All parameters are mandatory, and may have a default value, which will be used if the parameter is left untouched. The parameters are usually used by an application's Initialization script when configuring the application. For example, database credentials, logs location etc. The artifact is a binary file used by the Initialization script to install the application. The artifact’s details are usually used to specify the location in which the application's artifacts will be installed.
- Click Launch Sandbox.
- Once the deployment of your sandbox begins, an Open Sandbox button is displayed on the bottom of the screen. Click it to open the sandbox.
NOTE: In AWS environments, the applications may be inaccessible immediately after the environment becomes Active. This issue should resolve itself within a few moments when the AWS DNS propagation process completes.
For more information about launching sandboxes from your pipeline or using our API, see Launching Sandboxes.