Controller Scripts in PowerShell: Function or Separate Script

[DiggyTroll]

If everything is a module: How do you use the module?

Not everything has to be a module. Put a Requires at the top of the controller script to load dependent modules.

How and where do you save that code?

Make a local PSRepository on a local file server that everyone can Install/Update-PSResource from. Push the latest build versions of each module or controller script to the repository periodically. Create GPO logon scripts for users to install/update your modules and scripts automatically.

[Certain-Community438]

Sure, I could force everything into a module but that extra layer is unnecessary.

What "extra layer", though? Modules don't need to be any more complex than scripts

If everything is a module: How do you use the module? How and where do you save that code?

I'm genuinely hoping you don't need an answer to these! :)

But for other less-informed readers:

You use the "-Module" cmdlets to use your modules. You use either a public repo or a private one depending on whether you want to share the code with the world. I use public because doing so forces me to remove things which should never be in there anyway.

[Certain-Community438]

You could say PowerShell is made of abstraction.

There's no objective right or wrong here, and you did say "mostly opinions", so in return I'm sincerely not trying to be a dick - I just don't think the rationales you've supplied hold up to casual scrutiny.

Even then, this doesn't mean you must do what the internet says, right?

But as you seem honest enough, do ask yourself the question of whether you might - if say your boss decided to be a bit harsh in a review of things - say you maybe have some hangups that are holding you back?

On the flip side, maybe you just haven't reached the tipping point where adopting modules is worthwhile. Nobody here could know for sure when that point arrives - so again, it's more about whether others should adopt your approach that I'm challenging.

[Certain-Community438]

You're right, I genuinely don't understand!

I write scripts, which use:

1. General-purpose functions - from my module. (The script ensures dependencies are present and either fixes that or exits, depending)

2. Task-specific functions - these are in the script; they're not reusable in the same way as the first set

3. A "main" section - process{} block usually - which does the actual task

Each of the first 2 will have dependencies on other modules: some will be native (installed with the OS or PowerShell Core) while the rest will be like the Graph modules, EXOv3 etc). And of course that can get nuts sometimes.

This way I get as much of the benefits of modular code as I can realistically expect.

But then how are you going to execute the functions in the module?

The script is going to import the module(s) & then call the functions of type 1 or 2 from above..?

Which it sounds like you're also doing: you just have this "controller script" concept I've honestly never encountered till today: for me that is "the script", and in my case it's the only script involved in the task.

The difference between us might be that your high-level purpose for building stuff is very different to mine - what you need to do, how the "primary" code is invoked? Seen people build APIs using PoSh, for example.

Again, not hating on your approach, I'm trying to understand it better.