During a standard package deploy, Ive used the “custom install directory option”
I’ve also used variable substitution on config files / config transformation.
All this happens in an initial directory where the package is extracted to.
I’ve then also used config encryption.
I have a custom install directory as multiple copies / instances of the package can be installed on one machine (with different config).
I need to cleanup the package extraction folder ASAP to remove non encrypted config files.
Is there a variable I can use in a step after the deploy package step to ascertain the folder the package was extracted to?
Obviously with multiple pipelines deploying the same package (and sometimes the same version of the package) - the package extraction folder ends up being packageid\version.v.v_sequence
I did find some posts talking about a variable available within the step, but That variable didn’t contain anything in subsoquent steps (same server etc.).
Thanks for getting in touch! You can target the directory the package was extracted to in a couple different ways. The following system output variable contains this path which can be targeted in subsequent steps:
Replacing PackageStepName with your step name that deployed the package, you can target this in a subsequent script step to remove the contents.
Alternatively, you could embed this into a PostDeploy script inside your package step and use the variable:
Octopus.Action.Package.InstallationDirectoryPath
(This custom script would be run after the extracted package contents are copied to the custom installation directory, and you can reference the package deployment feature ordering in our docs. )
I hope this helps get you going! Don’t hesitate to reach out if you have any further questions or concerns moving forward.
)