[BUG] Usage of --split-per-config in a pipeline

[yafp]

Describe the bug
I am not sure if this is a bug - or a problem on how i use the setting (most likely).

I am using an Azure DevOps pipeline to create documentation. So far i was writing everything into a single file and it works as expected.

Now i considered - lets add another step to the same pipeline to generate in addition a split-per-config variant.
Since adding this step - the outcome in the defined folder is unexpected.

To Reproduce
The following works without issues in my Azure DevOps Pipeline - to produce just 1 big markdown file which contains everything

IntuneCD-startdocumentation \
              --path="$(Build.SourcesDirectory)/$(BACKUP_FOLDER)" \
              --outpath="$(Build.SourcesDirectory)/$(DOCUMENTATION_FOLDER)/as-built.md" \
              --tenantname=$(TENANT_NAME) \
              --decode \
              --intro="$INTRO"

But if i add another step into that pipeline to have both
a) a single markdown as shown above - and
b) multiple files - 1 per section

as shown here

IntuneCD-startdocumentation \
              --path="$BUILD_SOURCESDIRECTORY/prod-backup" \
              --split-per-config \
              --outpath="$BUILD_SOURCESDIRECTORY/$DOCUMENTATION_FOLDER_SINGLE/foo.md" \
              --tenantname="$TENANT_NAME" \
              --intro="$INTRO" \
              --decode

the outcome is just a single markdown file with 1 KB size and 2 lines

Expected behavior
I do expect that the outcome are multiple markdown files

Screenshots
If applicable, add screenshots to help explain your problem.

Run type (please complete the following information):

• Mode: [e.g. 0 or 1]
• Azure DevOps Pipeline
• Version 2.4.1

Additional context
Add any other context about the problem here.

[Lintnotes]

I am also seeing this exact behavior and the --split or -s param doesn't work at all either.

[almenscorner]

Tried it in a pipeline myself and for me it looks correct. What happens when -s or --split-per-config is used is that an index.md is created in the root of the repo which then links to the other markdown files created.

In the case of -s, it puts a MD per config type in its folder, i.e. Configuration Profiles.md for profiles.

In the case of --split-per-config it puts MD files per config in /docs in the configuration folder, i.e. Device Configurations/docs/config.json.

Do you get the index file which links to the other MD files where the specific config is actually documented?

[Lintnotes]

i can confirm that does indeed work sorry i didn't fully grasp that from the documentation.

[almenscorner]

Wiki improvements are welcome 😄