We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
IdentityPreProcessor
MigrateIdentityPreProcessor
IsEnabled
migrated-identities
Does this seem like a sensible approach?
The text was updated successfully, but these errors were encountered:
@aseanferguson any thoughts regarding this approach?
Sorry, something went wrong.
That works for me. Just make sure you use the domain format and not just their name.
No branches or pull requests
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.
The processors are the part I'm making sense of still though.
IdentityPreProcessor
, maybeMigrateIdentityPreProcessor
.IsEnabled
to look for any list in themigrated-identities
field. Any items in this lists would be the litmus test for enabled/true.migrated-identities
replace it with the new one.Does this seem like a sensible approach?
The text was updated successfully, but these errors were encountered: