* Initial commit with all but one unit test functioning correctly.
Confirm-Resource.Tests.ps1 is failing due to "Unable to find type [ResourceType]", which makes no sense, since Get-ResourceByType uses the same enum, but the unit tests pass without issue.
* Merged examples into grouped folders.
Removed modules from the psd1.
* Added a build script that can be used both during development and to build the final .psm1 for publishing to PS Gallery.
* Minor code cleanup.
* Updating CI/CD workflows.
* Updated the installation and contributing docs.
* Moved pr-psgallery.yml workflow into ci.yml. Now that there is a "build" process for the module this should happen in the CI pipeline and not the PR pipeline.
* Fixing working directory for unit tests.
* Swapped out relative paths for the PS Gallery module name in the examples, because the relative path will no longer work without building the module.
* Moved the ci-publish-docs-branch.yml into the ci.yml. It made sense logically once I tried rewriting it after the refactor.
* Fixing broken reference in the 'ci_cd_workflows.md' file.
* Minor update to 'ci_cd_workflows.md'
* I honestly couldn't figure out why `ResourceType` was not able to be found. I tried every which way of `using`/`Import`ing/dot sourcing that can be imagined. I think that this is a fundamental issue with PowerShell. The more I researched the more I found about enums and classes not being available from nested modules. I'm not sure why the classes work and enums do not though.
* Fixing broken unit test's reference to `ResourceType.psm1`.
* Adding local environment setup to CONTRIBUTING.md
* Adding in megalinter info and some minor changes.
* Fixing linter warning.
* Minor clarification.
* Updating the docker command for megalinter to remove the container when finished.
Engin Polat
marclerwick
Ozi Boms