Runbook specific variables

Octopus allows you to define variables and scope them for use in different environments when running a Runbook. Variables allow you to have a consistent Runbook process across your infrastructure without having to hard-code or manually update configuration settings that differ across environments, deployment targets, channels, or tenants. In addition to environments, you can scope variables to specific Runbooks.

1. From the Hello world project you created earlier, click Variables in the left menu.
2. Enter Helloworld.Greeting into the variable name column on the first row of the table.
3. Add Hello, Development Runbook into the value column.
4. Click the Scope column and select the Development environment and Hello runbook process.
5. Click ADD ANOTHER VALUE button.
6. Add Hello, Test Runbook and scope it to the Test environment and Hello runbook process.
7. Click ADD ANOTHER VALUE button.
8. Add Hello, Production Runbook and scope it to the Production environment and Hello runbook process.
9. Click the SAVE button.

Steps in the runbook process can reference the variables.

1. Click Runbooks on the left menu.
2. Click Hello Runbook in the list of runbooks.
3. Click Process in the runbook menu.
4. Select the script step.
5. Change the script in the script step based on your language of choice:

Write-Host $OctopusParameters["Helloworld.Greeting"]

greeting=$(get_octopusvariable "Helloworld.Greeting")
echo $greeting

6. Click the SAVE button.
7. Click the RUN… button, select and environment, and run the Runbook.

The next step will add deployment targets to run runbooks on.

Further Reading

For further reading on Runbook variables please see:

• Runbook Variables
• Runbook Documentation
• Runbook Examples

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Tuesday, July 30, 2024