Migrator does not remap account variables correctly when importing

[michaelnoonan]

Imagine you have some project variables for AWS or Azure accounts. These are deep links (via database ID) to an actual AWS or Azure account, nice right?

When you use the data migrator to export and then import a project, the AWS and Azure account variable values (the IDs) are not remapped correctly from the source to target. This means you may not be able to open the variable editor for the project, or a deployment of this project will either fail, or it will use the wrong account because the ID was valid but pointing to the wrong account.

What I expected to happen

Any AWS or Azure account ID should be remapped correctly from the source to target when importing.

Affected versions

Octopus Server: 2018.2 until fixed.

Workarounds

Nothing good.

[michaelnoonan]

VariableSetImporter doesn't cater for typed variables, other than Certificate

[octoreleasebot]

Release Note: migrator.exe now correctly handles importing account variables, where before the account variable was not remapped correctly from source to target

[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.