search

merddyin / ADDeploy

Used to deploy components to support an ESAE forest and RBAC model via native control.
MIT License
2 stars 0 forks source link

Plugins folder name "splitepipeline" is wrong #7

Open PatrickOnGit opened 1 year ago

PatrickOnGit commented 1 year ago

The plugins folder containing the module splitpipeline is named wrong, preventing the module to load.

merddyin commented 1 year ago

I will look into this, however the plugin module has been loading correctly for me. The plugins are discovered automatically during the load process by finding a load.ps1 file...so long as that file has the correct sub-path, then the module should regardless of spelling.

PatrickOnGit commented 1 year ago

Maybe, as the build process did not work and I used the code "as-is", without explicitly building it, it failed. So I fixed the path. After I fixed the build process I actually didn't check if it would work with the wrong path name ;-)

merddyin commented 1 year ago

So it looks like I fixed this at some point in the past. It really only kicks in as a need when deploying to large environments. The Dev branch, which has v1.4.6 has the corrected path. That said, the orchestration cmdlet (Publish-ADDESAEStructure) hasn't been updated yet to use all the updated cmdlets, so you would not be able to take advantage of the splitpipeline.

If you are currently needing the splitpipeline functionality, due to a large environment, you can either rename the folder in your local copy, or you can update the load.ps1 file in the plugins folder for splitpipeline. Now that I have the latest version up, I have several items on my urgent list...namely a couple of bug fixes and then updating the orchestration cmdlet.

PatrickOnGit commented 1 year ago

I corrected the path in my copy to make the module load. The split pipeline process had a couple of issues and are even more tricky to debug which is why, in the end, we didn't use it.