vsts-work-item-migrator

vsts-work-item-migrator copied to clipboard

More of a design question here.

Looking into adding a feature which can replace identities from local AD accounts in TFS to ones in Azure AD accounts in VSTS.

High-level design was to introduce another key into the configuration files.

migrating-identities = [
{"source": "anger1", "target": "[email protected]"},
{"source": "bill", "target": "[email protected]"}
]

The processors are the part I'm making sense of still though.

1. Make a new processor similar to the IdentityPreProcessor, maybe MigrateIdentityPreProcessor.
2. Override IsEnabled to look for any list in the migrated-identities field. Any items in this lists would be the litmus test for enabled/true.
3. Read through source WIs and when I come across one of the migrated-identities replace it with the new one.
4. Have it run prior to IdentityPreProcessor so it still can have the affect to create those identities.

Does this seem like a sensible approach?

@aseanferguson any thoughts regarding this approach?

That works for me. Just make sure you use the domain format and not just their name.