Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect certificate variable scoping when using tenant tags #3669

Closed
distantcam opened this issue Jul 17, 2017 · 2 comments
Closed

Incorrect certificate variable scoping when using tenant tags #3669

distantcam opened this issue Jul 17, 2017 · 2 comments
Assignees
Labels
feature/tenants kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@distantcam
Copy link

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:

  1. Create two tenant tags, Foo and Bar.
  2. Add two certificates, using Foo and 'Bar' tenant tags in restriction respectively.
  3. Add two tenants, with Foo and 'Bar' tags respectively.
  4. 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.
  5. Add a process step, simply run script Write-Host $OctopusParameters['Certificate']
  6. Hook the two tenants to the project.
  7. Create a release, deploy to any of the tenants.
@distantcam distantcam added kind/bug This issue represents a verified problem we are committed to solving feature/tenants labels Jul 17, 2017
@distantcam distantcam self-assigned this Jul 17, 2017
@octoreleasebot octoreleasebot added this to the 3.15.7 milestone Jul 19, 2017
@octoreleasebot
Copy link

Release Note: Fixed a problem where certificate variables were not being scoped by tenant tags

@lock
Copy link

lock bot commented Nov 24, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/tenants kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

2 participants