Finnian Dempsey

I've reproduced this issue on version >=0.11.1, and confirmed that if a variable matches another variables name and environment, then it will be targeted for future apply's. Using the following...

Hey @esaporski, no worries! It looks like a solution is definitely being worked on however I can't give an exact timeframe of when it will be released. There are a...

Additional request - [Internal Link](https://octopus.zendesk.com/agent/tickets/126715)

Hey @twistypigeon I've just tested and confirmed the workaround is still functioning, did you use the `Run a Script` type step instead of `Run an AWS CLI Script`? If a...

[Another Customer Report](https://octopus.zendesk.com/agent/tickets/81605) [Internal Slack Discussion](https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1641361992340400)

The investigation into this issue determined that this is the intended functionality and there is another method to use. To have different certificate values scoped to each tenant, navigate to...

[Another report](https://octopus.zendesk.com/agent/tickets/77088) of this issue.

This has been fixed in Octopus Server 2024.3.1246, see https://github.com/OctopusDeploy/Issues/issues/8818

@3guboff Typically reference packages use the Step name and Package Reference, which looks to be required for packages that include a `/`, the following format should work: ``` octopus release...

Great to hear @3guboff! The wording is definitely a little odd but I believe it's indicating that for packages 2 formats are available ({package}:{version}, {step}:{version}) however for referenced packages there...