We’re happy to announce that it is now possible to have Torque send sandbox event notifications to the Teams/Slack channel, or automation tool, of your choice. You can define multiple notifications for different communication tools, and for different channels in the same communication tool. For details, see Configuring Torque Notifications.
To launch a sandbox from the blueprint:In the Blueprints page, click the suitable blueprint's Launch Sandbox button.The sandbox details form is displayed, with a default sandbox name. Optionally change the sandbox name. Fill in the sandbox details, as explained in Launching a Sandbox From the UI. Click Launch Sandbox.
We’ve added a Launch Sandbox button to the blueprints, allowing you to conveniently launch your sandboxes directly from the Blueprints page.
After installation you will have two stages added to your Spinnaker stages list:Start Sandbox StageBlueprint Name - Provide the name of the blueprint to be used as a source for the sandbox. Sandbox Name - Provide a name for the sandbox. Space Name - The name of the Torque Space your repository is connected to. Artifacts - [Optional] A comma-separated list of artifacts per application. These are relative to the artifact repository's root defined in Torque. Example: appName1=path1, appName2=path2. Inputs - [Optional] You can provide the blueprint's inputs as a comma-separated list of key=value. For example: key1=value1, key2=value2. Timeout - Set the timeout to wait (in minutes) for the sandbox to become active. If not set, an action just starts a sandbox and returns its ID without waiting for 'Active' status. Duration - Set the sandbox duration in minutes. The sandbox will automatically de-provision at the end of the provided duration. Token - [Optional] Provide the long term Torque tok
This plugin integrates Torque into your Pipelines in Spinnaker 1.23.0 and above.Add the following to the Halyard config (typically found at ~/.hal/config) to load the Orca backend. spinnaker: extensibility: plugins: Quali.TorqueSandboxPlugin: id: Quali.TorqueSandboxPlugin enabled: true version: <<VERSION NUMBER>> config: torqueToken: <<API Token (Not Required) >> torqueUrl: <<API URL (Not Required) Default= https://qtorque.io >> account: <<Torque Sub Domain (Not Required) >> repositories: TorqueRepo: id: S3Repo url: https://raw.githubusercontent.com/QualiTorque/torque-spinnaker-plugin/master/plugins.json torqueToken is the authentication token used by default but is no longer required. You can specify the Torque token used by each stage in the Spinnaker pipeline. Add the following to gate-local.yml in the necess
This article explains how to configure Torque notifications for Slack chats, Teams chats, and your preferred automation tool(s). You can define multiple notifications for different communication tools, and for different channels in the same communication tool.The target chat or automation tool is defined by a dedicated webhook, which you will need to provide. To configure Torque notifications:In Torque, access the suitable space. Click Settings > Notifications. Click + Add Notification. The Select the notification target dialog box is displayed (Slack, Teams, or generic webhook). Select the suitable communication tool. Provide a name for the notification. Enter the webhook address, as explained in the desired tool’s official documentation. For Slack, see https://api.slack.com/messaging/webhooks. For Teams, see https://techcommunity.microsoft.com/t5/microsoft-365-pnp-blog/how-to-configure-and-use-incoming-webhooks-in-microsoft-teams/ba-p/2051118. For your preferred automation tool,
In the coming days, we will release Torque Notifications, enabling space admins to define notifications for sandbox lifecycle events. The notifications will be sent to Teams or Slack chats, or the automation tool of your choice.Supported sandbox events:Sandbox started Sandbox ready Sandbox ended Sandbox active with errors Sandbox ended with errors
We’ve added support for dynamically populating inputs to Helm charts. You can use this capability to add, to your application quick links, variable inputs that auto-populate during the sandbox’s deployment. For details, see the Inputs and Quicklinks sections in Creating a New Blueprint From a Helm Chart.
Providing you with visibility into the costs of your sandbox executions, Torque now displays the estimated and current costs for each blueprint and sandbox.The costs are displayed in the Blueprints page:When selecting a blueprint for the sandbox:When setting the sandbox’s duration:And in the sandbox’s details page:The costs are based on the blueprint’s past executions. This capability is not supported for EKS/AKS.
GitLab, a major code collaboration and version control, is now a first-class citizen in Torque. Teams can now associate YAML and Terraform module repositories residing on GitLab. Go to your space’s Settings > Repositories page, click Add a Repository, select the GitLab icon, specify the repo’s URL and click Connect.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.