You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting up tenants using tags, if you provide copies of the same project variable, and scope each copy to a tenant using tags, the scope is ignored when deploying.
Add two certificates, using Foo and 'Bar' tenant tags in restriction respectively.
Add two tenants, with Foo and 'Bar' tags respectively.
Create a project, add two certificate variables both called Certificate using the two certificates respectively. In each of the variable scope setting, add Foo and 'Bar' tenant tags respectively.
Add a process step, simply run script Write-Host $OctopusParameters['Certificate']
Hook the two tenants to the project.
Create a release, deploy to any of the tenants.
The text was updated successfully, but these errors were encountered:
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.
lockbot
locked as resolved and limited conversation to collaborators
Nov 24, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When setting up tenants using tags, if you provide copies of the same project variable, and scope each copy to a tenant using tags, the scope is ignored when deploying.
Reported here (private link) http://help.octopusdeploy.com/discussions/problems/55928
Steps to repro:
Foo
andBar
.Foo
and 'Bar' tenant tags in restriction respectively.Foo
and 'Bar' tags respectively.Certificate
using the two certificates respectively. In each of the variable scope setting, addFoo
and 'Bar' tenant tags respectively.Write-Host $OctopusParameters['Certificate']
The text was updated successfully, but these errors were encountered: