Support for splitting YML into smaller files

[josearesvi]

As mentioned in the section "Maintaining Large YAML Definitions By Splitting Them" we have do so and in our pipeline we have 2 commands:

dotnet-apim -c ".\Products-Config.yml" -o "$(Build.ArtifactStagingDirectory)/Dev" -f ".\EnvironmentConfigurations\config-dev.yml" -p "dev-"
dotnet-apim -c ".\APIM-Subscriptions-Config.yml" -o "$(Build.ArtifactStagingDirectory)/Dev" -f ".\EnvironmentConfigurations\config-dev.yml" -p "dev-"

The first one creates a Product that then the second one ( Subscriptions ) will use to set permissions, still the 2 .yml are not aggregated into one single dev-apim_deploy.template.json file, what it seems to happen is that the last overrides the first one. How should we run this so that the Products-Config.yml and the APIM-Subscriptions-Config.yml are aggregated into a single deployment definitions.

[emaeric25]

@josearesvi This seems to me to be an error in the documentation. Because if you put your input files (Products-config.yml and APIM-Subscriptions-Config.yml) in the same folder (e.g. Config) and reference that, it seems to work.

So then your command gets (with Config as a new folder with the two config files in it) :
dotnet-apim -c ".\Config" -o "$(Build.ArtifactStagingDirectory)/Dev" -f ".\EnvironmentConfigurations\config-dev.yml" -p "dev-"