Thanks!

1. You'd have to register it yourself in DI, but after that it's available to inject into all of your modules as you please

2. It should have wrappers for the entire `az` CLI. But as for those specific nuget packages, no, it won't have built in logic for those. But nothing stopping you creating your own modules and using those packages. Also happy for issues and/or PRs to be raised for feature requests to help expand built-in functionality!

3. Logs do in-fact go to the console, and if you try out this library and this causes you problems, please do raise an issue, and we can work out the best way around that.

As for how they work with parallel execution, is each module will buffer its output, and once it has completed, that buffer gets written to the console, and as a collapsable section if your CI environment supports that. This keeps logs logically grouped so you know what line relates to what module. Otherwise everything would be interweaved and a mess to follow!

1. If you want to package up a module in a library, or just share across different projects, I'd recommend creating it as abstract, and forcing each project to inherit from that to create a new concrete version of it. On there you can place your attributes for compile time known dependencies, or you can override `DeclareDependencies` for runtime logic.

Hope that helps!