16.3.1 version contains 'missing' and 'missing2' in Source parameters - is that correct??

[EdPerminas]

"MigrationTools": {
"Version": "16.0",
"Endpoints": {
"Source": {
"EndpointType": "TfsTeamProjectEndpoint",
"missing": "https://dev.azure.com/nkdagility-preview/",
"missing2": "migrationSource1",
"AllowCrossProjectLinking": false,
"ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",

[MrHinsh]

Nope. Please read the documentation on https://devopsmigration.io

[EdPerminas]

What is the reason then to keep it? That breaks schema validation.

[MrHinsh]

Not sure what you mean. missing and missing2 are not valid. Where did you get them from?

They are not in the schema.

The only place it appears is in my test data in configuration-default.json, which is there to validate that the Schema correctly identifies them as invalid.

[EdPerminas]

Accidentally deleted previous comment. @MrHinsh - just download 16.3.1 and check configuration-default.json. It's under Source parameters.

[MrHinsh]

Yes, configuration-default.json is test data.

[EdPerminas]

@MrHinsh - alright, fair enough. A comment or something like configuration-default-test.json would be really helpful.