Do we support REST API call instead of Object Model?

[hachi1030-Allen]

Describe your issue:

I am getting 500 internal server error from Azure DevOps service and it's caused by too many projects in the org. This is triggered by Azure DevOps because by running the tool, we are using Object Model.

Source Details

Azure DevOps Services

Target Details

Azure DevOps Services

Error screenshot

[hachi1030-Allen]

@MrHinsh Please help to take a look and simply let me know if this tool supports calling to REST API now.

Thanks!

[MrHinsh]

It does not, the tool is based on the Object Model.

[hachi1030-Allen]

It does not, the tool is based on the Object Model.

Thanks Martin for the reply.
Do we have any schedule on implementing that? Is it on the roadmap or not?

[MrHinsh]

Not on the roadmap. Kinda!

We have initial work ongoing (slow) to move the system to a model that allows interoperation between different systems. That way, you could migrate from OM source to Rest target. However, this has been slow.

I am only actively working on this when I am working on migrations.

We still do a significant number of migrations for pre-Rest environments and that makes the investment dificult.