Octopus.Environment.Name not evaluated when manually running a step template from library

[alexrolleyoctopus]

To replicate issue:

• Create a step template based off default script template
• Add code to evaluate system variable $EnvironmentName = $OctopusParameters['Octopus.Environment.Name']
• Manually run script template
• Select Run the script on all deployment targets in set of environments and roles
• Limit it to an Environment
• Select run now

You will notice that the variable evaluates to null, whereas the same code when run as a script step in a project will correctly report the Environment.

[octoreleasebot]

Release Note: Add help text to environment selector on Run Step template page to make it clear no environment variables are available

[stanislavhordiyenko]

Interesting solution to solve the issue 👎

[hnrkndrssn]

Hi @stagor,

The release note doesn't have the full explanation of the solution that we have put in, the reason that we only added a note about no environment variables being available is due to that the Run step template feature is based on the Script console feature and by design these scripts are only run in the context of a machine, so unfortunately we don't have access to any environment variables.

My apologies for the inconvenience caused.

Thank you and kind regards,
Henrik

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.