Guide: How to Deploy a Recipe
Learn how to deploy a recipe for self-service
Step-by-step
In the example below, we’ll be deploying a simple workflow recipe for Google Cloud Storage. Follow these steps below to deploy your recipe:
Navigate to your Deploy page
Navigate to the Deploy page from the navigation menu on the left of your Tempest web console.
You’ll find your recipes displayed here. For example, here’s a Deploy page with a workflow recipe for Google Cloud Storage.
Deploy page with workflow recipe for Google Cloud Storage
Select the recipe you want to deploy
Once your select the recipe you want to deploy, you’ll be taken to a preview of the recipe. Here you can find details on who owns the recipe, what resources it will create, and more. You’ll also be able to share the recipe from this preview.
Preview of a workflow recipe for Google Cloud Storage
Next, click on the Deploy Now button to configure the recipe.
Configure the recipe
After clicking Deploy Now, you’ll be taken to the recipe configuration page. Here you can add any configuration needed to deploy the recipe.
The configurable options here are defined by your recipe. For instance, in this recipe, we made the Storage Bucket Name field a user-defined variable.
How your users will self-service your recipes
You can also expand the “Review your Workflow’s configuration” section to see a preview of the resources that will be created. Once you’re satisfied with your configuration, click Create Project to deploy your recipe.
Review your deployed project
Once your recipe is deployed, you’ll be taken to the project’s page. Here you can find details on the resources that were created, as well as any logs or errors that occurred during the deployment.
Logs for a deployed workflow for Google Cloud Storage
Now that you’ve deployed your recipe, this will be the homepage for your project. You can attribute owners, add links, and more. The information about your provisioned resources are automatically collected and accessible from your project page.
Let’s take a look at the resource we created.
The Google Cloud Storage bucket we created
From here, you can open the resource in the external provider—in this case, Google Cloud Storage—to see the storage bucket resource we created. Or you can open the resource directly in Tempest.
The Google Cloud Storage bucket resource we created