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

Migrator does not remap tenant variable scopes correctly #5087

Closed
michaelnoonan opened this issue Nov 13, 2018 · 3 comments
Closed

Migrator does not remap tenant variable scopes correctly #5087

michaelnoonan opened this issue Nov 13, 2018 · 3 comments
Assignees
Labels
feature/migrator kind/bug This issue represents a verified problem we are committed to solving size/tiny ~1 hour
Milestone

Comments

@michaelnoonan
Copy link
Contributor

Imagine you have a variable value which is scoped to a set of tenants by a tenant tag query. If you export a project and then import it into another server, the tenant tag scope is not remapped correctly from the source to the destination server. This would result in the variable value not being used in the correctl deployments, or even prevent you from loading the variable editor correctly.

What I expected to happen

The tenant tag scopes should be mapped correctly from the source to the target server.

Affected versions

Octopus Server: 3.4

Workarounds

Nothing good.

@michaelnoonan michaelnoonan added kind/bug This issue represents a verified problem we are committed to solving feature/migrator size/tiny ~1 hour labels Nov 13, 2018
@michaelnoonan michaelnoonan self-assigned this Nov 13, 2018
@michaelnoonan
Copy link
Contributor Author

@octoreleasebot octoreleasebot added this to the 2018.9.9 milestone Nov 14, 2018
@octoreleasebot
Copy link

Release Note: migrator.exe now correctly handles importing variable values scoped to tenants via tenant tags

@lock
Copy link

lock bot commented Feb 12, 2019

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 Feb 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature/migrator kind/bug This issue represents a verified problem we are committed to solving size/tiny ~1 hour
Projects
None yet
Development

No branches or pull requests

2 participants