A container for using IntuneCD with version locked pipenv to try and mitigate supply chain attack posibilities
IntuneCD or, Intune Continuous Delivery as it stands for is a Python package that is used to back up and update configurations in Intune.
Pipenv was used here initially because of the specificity of the Pipfile.lock syntax. While not as easily human readable as other methods of python dependancy version/hasing, it is easier to get to an installed and working environment.
This has been switched to using a traditional requirements file, wish hash information included. This provides equivelent supply-chain safety with fewer dependencies during deployment. For information on how the requirements with hashes is generated, please see requirements_version_locker
Clone this repo to somewhere, and build it with docker-compose build
I recommend making modifications to the docker-compose.yml file and adding in appropriate command line switches in the command: section, for your tenancy. Alternatively if you wish to supply information via the environment variables method as per official documentation then do so within the environment: section.
Obviously you can use the volume: section to map in a json configuration file for IntuneCD, and map in an output folder for the IntuneCD generated documentation.
Please open an issue for support
Please contribute using Github Flow. Create a branch, add commits, and open a pull request