Deploy fails when dependant LS does not exist yet about vsts-publish-adf HOT 5 CLOSED

The deploy task doesn't parse the input and therefor it doesn't determine dependency; the major reason behind that is the task doesn't need to know the JSON schema and will keep working if the schema is changed regarding dependency e.g.

If you need dependency, you have to build it yourself. Several options are:

• Define order by prefixing the filenames, e.g. 01_
• Combine sort order and change the parallel tasks in the advanced section to force a strict order
• Create multiple steps to deploy the JSONs in the correct order

Currently I am thinking about to add multiple stages to the deploy task for easier maintenance.

-JP

from vsts-publish-adf.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from vsts-publish-adf.

Jan, due to this limitation, I created Custom Task for Azure DevOps Pipeline from scratch which is free of such limitations: DataFactoryTools
Forgive me for pointing here to another tool, but I believe it's worth mentioning because many people struggling with the same issue, i.e. dependencies. IMHO, renaming objects is not the correct solution people should go towards.

from vsts-publish-adf.

The current version (v2.3.3) contains support for the detection of pipeline/linked service dependencies in combination of parallel task execution. You can add detectDependancy: true to your pipeline definition to enable the detection.

from vsts-publish-adf.

activating "Detect object dependancy" in release pipeline, the error persists

from vsts-publish-adf.