Handling dependencies between applications
In real-world Dynamics 365 Business Central projects, it’s absolutely common to create extensions with dependencies from other extensions. When working in teams of developers, a best practice when you have multiple extensions is to create separate repositories; one repository should contain one extension.
For AL-Go for GitHub to handle the CI/CD pipeline of an extension that has a dependency from an extension stored in another repository, the dependent repository must be added to the dependency probing paths (appDependencyProbingPaths parameter) in the AL-Go settings file.
To show that, in my GitHub repository, I’ve created a new per-tenant extension (named DependendApp) with the AL-Go for GitHub template, as previously explained.
In the app.json file of this second extension, I’ve added a dependency from another app (the previously created DemoApp) that is physically stored in another repository on GitHub...
