Runbook access to package deployment path


I seem to be stuck on a Runbook-related problem with no obvious answer.

Let’s say we have a Project X which deploys package P1 to Environments E1 & E2.
There is a need to have post-deployment actions which manipulate the disk content of a deployed release (at path c:\Octopus\Applications\TENANT\ENV\PACKAGE\VERSION).

An example of such action: changing the theme of a website by ‘swapping out’ image folder names. Another example: adding ‘app_offline.htm’ to the package folder.

It would seem that a Runbook is a perfect way to implement this. However, within the context of a Runbook, there is no access to the installation location of the most recent Release for, say, {Package P1 + Environment E2}. The output variables of the Project’s Process (including ''Output.Package.InstallationDirectoryPath) are simply not available in a Runbook.

Octopus certainly knows the newest deployed version and deployment folder paths for every combination of {Package + Environment}; how can we access the same data from within a Runbook?

Thanks for your ideas!

Hi @t.zilinskas,

Welcome to the Octopus Forums.

Thanks for reaching out.

Each deployment actually creates a variableset with the variables used inside of it that you can reference.

You will need to look at api/deployments to find the deployment youre looking for. Within deployments/api, you will find something like:

You will then take that variableset ID and you can get the information you need within api/variables/variablesetidyoufoundindeployments

The pseudo-code would be:

Do an API call on api/deployments, find the one you want based on environment/space/project/etc
Store the manifestvariablesetid to a variable.
Do an API call on api/variables/$variablesetId
Parse the json for the required variables.

Please let me know if that worked for you or if you need further help.


Thank you!

It just seems strange that one is forced to access a chunk of Octopus’ data via REST… while executing within Octopus itself. An in-proc shortcut would be very beneficial; accessing deployment folder from a Runbook would seem a rather common use case (e.g. reading accumulated logs).

In any case, the path is clear :slight_smile:

1 Like

Hey @t.zilinskas,

Thanks for letting me know that it works for you. I appreciate the feedback I will pass it along.

Please let me know if you need any help with it as you get it going.

I hope you have a great rest of your week.


This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.