Migrator does not export ExtensionConfiguration documents

[lawrencewilson]

When making a new export using Octopus.Migrator.Exe, the ExtensionConfiguration does not get added to the export as expected.

Steps to reproduce

1. Login to Windows on the Octopus Server
2. Run an export using the command prompt:

Octopus.Migrator.exe export --directory="C:\tmp\export" --password="superSecurePassword" --instance="nameOfInstance"

3. Navigate to the exported directory for ExtensionConfiguration (in this case C:\tmp\export\ExtensionConfigurations)
4. Look at one of the documents, for example: AzureAd.json

#Expected Results
The Extension gets exported to this json document form the Octopus Database

#Actual Results:
We see "Json": null where we would expect to see exported content from the Octopus Database

{
  "$type": "Octopus.Core.Model.Extensions.ExtensionConfiguration, Octopus.Core",
  "Id": "authentication-aad",
  "Name": "AzureAD",
  "ExtensionAuthor": "Octopus Deploy",
  "Json": null
}

Affected versions

Octopus Server:2018.8.6

Links

https://help.octopus.com/t/octopus-migrator-no-longer-supports-extensionconfigurations/21419/4

[Jaykul]

Will this ever be fixed?

[michaelnoonan]

HI @Jaykul - This has been on our backlog for a bit too long. Let me take a look at it again.

I'm assuming you've reached out because this issue is affecting you? Can you let me know some details about what you're trying to achieve? Thanks!

[michaelnoonan]

Migrator does not export ExtensionConfiguration documents

[michaelnoonan]

Ah, I just found your forum thread @Jaykul - let me investigate and get back.