Requirements
Powershell_CICD_repository
Requirements | Powershell_CICD_repository | |
---|---|---|
4 | 2 | |
156 | 111 | |
0.0% | - | |
0.0 | 4.4 | |
over 1 year ago | 7 months ago | |
PowerShell | PowerShell | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Requirements
-
Hyper-V clusters declarative
Does noone manage Hyper-V clustered VMs properly using declarative approaches? I cannot find a single complete approach to managing it. puppet, salt, terraform, even DSC have limited use cases and focus on single node VM creation. System Ctr is is obsolete trash. I was thinking of building something custom using a project (semi-non maintained) here https://github.com/microsoft/Requirements and building out getters and setters but figured I would see if someone has solved for this. It's a shame terraform provider isn't being actively updated because thats probably the most correct way or if bicep/arm templates could be used against on-prem HyperV. Not sure how people can manage this thing without a sane devops approach.
-
Best approach for creating the IaC for an existing Azure landing zone?
You might benefit from something like Requirements, though you'd probably want to fork rather than use the module which doesn't support pwsh7.
-
"maintaining state is an imperative loophole that breaks the declarative paradigm" Thoughts?
Found the statement above in a repo. Would like to get some opinions on this.
-
Tiny Changes, Reliable Impact
The Requirements framework itself is quite simple to work with. There is a gotcha about using abstractions and control flow statements. You'll need to call .GetNewClosure() to ensure variable values are captured within the defined scriptblocks. The challenging part is breaking down the necessary desired state into its atomic components. A lot of the tools we use try to be helpful and change a lot of system state with a single command. That's great for some informal command-line work, but when you want a reliable script, building a declarative, idempotent script is going to save you time and effort in the long run.
Powershell_CICD_repository
-
PowerShell AST, your friend when it comes to PowerShell code analysis & extraction
I get it. I have something very similar in my powershell ci/cd solution too https://github.com/ztrhgf/Powershell_CICD_repository 😉
-
CI CD for PowerShell scripts in Active Directory environments
please check my free solution at https://github.com/ztrhgf/Powershell_CICD_repository or short introduction video at https://www.youtube.com/watch?v=-xSJXbmOgyk
What are some alternatives?
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Citrix-VDI-Profile-Reset-Tool - VDI Profile Reset Tool
NPSLogFile - Module for interpreting NPS/IAS Logfiles in PowerShell
SCOM-Scripts-and-SQL - The Scripts provided here are compatible with System Center Operations Manager
PowerShell - PowerShell scripts for Mick's IT Blogs
DotFetch - An alternative to NeoFetch on Windows
powershell-git-aliases - :octocat: Oh My Zsh's Git aliases for PowerShell.
azure-powershell-migration - Tools and resources to help migrate PowerShell scripts between incompatible versions of Az and AzureRM modules
Pode - Pode is a Cross-Platform PowerShell web framework for creating REST APIs, Web Sites, and TCP/SMTP servers
PSPKI - PowerShell PKI Module
AzOps - AzOps is a PowerShell module which deploys (Push) ARM Resource Templates & Bicep files at all Azure scope levels and exports (Pull) ARM resource hierarchy.
AsBuiltReport.Microsoft.AD - Repository for AsBuiltReport Microsoft Active Directory module