[FEATURE] Decode additional properties in base64

[aaronparker]

Here's additional payloads that are in base64 format. Apologies, I should have checked for more - this is what's in my current as-built, so there could be more properties.

• microsoft.graph.win32LobAppPowerShellScriptDetection
• microsoft.graph.win32LobAppPowerShellScriptRule
• microsoft.graph.win32LobAppPowerShellScriptRequirement

Each of these has a property of scriptContent in base64 format.

[almenscorner]

Question is, do you want a potentially large script documented in line in the PDF?

[almenscorner]

Granted I'm not a Windows expert and don't really know how large these scripts can be, just asking ☺️

[aaronparker]

I say yes - could decoding be an optional parameter?

Because I'm automating the as-built with IntuneCD, it doesn't matter how long the PDF is.

[almenscorner]

@aaronparker, I have added the -d argument to IntuneCD-startdocumentation in #112. When set, IntuneCD will attempt to detect all base64 strings and decode them in the documentation.

You can test it by installing the latest beta -> pip install IntuneCD==1.4.7b1.

[aaronparker]

Works great. 👌

It does create some strange rendering issues which must be a result of special characters in the scripts. However, the document formats better, especially a PDF.

HTML view of the above

[almenscorner]

As long as the MD and PDF looks good I think it's enough :)