Server-QA-Checks
Configuration
Server-QA-Checks | Configuration | |
---|---|---|
2 | 6 | |
74 | 173 | |
- | 1.2% | |
10.0 | 3.8 | |
about 1 year ago | 9 months ago | |
PowerShell | PowerShell | |
Apache License 2.0 | 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.
Server-QA-Checks
-
what what's the first thing you used Powershell for?
Like right at the beginning of my PowerShell journey? Version 1 (unreleased) of my QA Checks. This is v3, fully compatible with PowerShell 2.
-
Powershell 2.0
This is PS2 compatible: https://github.com/My-Random-Thoughts/Server-QA-Checks/blob/master/engine/Check-Port.ps1
Configuration
-
How to use config files for modules?
There's a configuration module I've used here. You can export a hashtable config to a .psd1 file, which you can import with Import-PowerShellDataFile
-
Best practice? How to leverage a .psd1 config file for a module
What i've decided on recently was that there should be config file, or settings file, that contains the default values I would normally supply to this private function. I've read the ramblingcookiemonster blog about config data: http://ramblingcookiemonster.github.io/PowerShell-Configuration-Data/ and I've read about the Configuration module and PSDkit module. My preference would be to write my own code for my purposes.
-
Creating a 'reference' list similar to the output of 'Get-Verb'?
Thanks! I dunno how i missed going over CSV and arrays, because I literally JUST got the hang of hashtables working on another project of mine dealing with psd1 files and using them as script/module config files in a manner similar to PoShCodes Configuration module (https://github.com/PoshCode/Configuration) but much simpler, without all the added complexity, as all i needed it for was as a place to store variables corresponding to paths, aliases, and a few misc values. and had to learn how to structure hashtables and how to read values from them to do it. Ill definitely read back up on it and give it a try and post back when i get something working, thanks!
-
Config Files for PowerShell Modules
I tried several of these as well, my favorite was https://github.com/PoshCode/Configuration
-
Trying to rework some older scripts with better habits... Let's discuss!
For "global variables", I think what you're looking for is some sort of configuration file. I personally use a PSD1 file, but others may prefer json, XML or YAML. There is also a module on github called Configuration that may be useful.
-
Best Practice for not overwriting certain data when pushing shared module/library updates
If you don't want to re-invent the wheel, you could take a dependency on and use something like https://github.com/PoshCode/Configuration
What are some alternatives?
QA-Checks-v4 - PowerShell scripts to ensure consistent and reliable build quality and configuration for your servers
scripts - My random scripts
PsdKit - PowerShell data (psd1) tool kit
infraspective - Infrastructure testing using pester
PowerShell_Credential_Manager - PowerShell Module to Read and Write Credentials from the Windows Credential Manager
CollectAllLogs - Welcome the the script repository of Customer Engineer (PFE) Russ Rimmerman.
My-PowerShell-Configuration - Repository for my personal PowerShell Profile(s), modules (ones I havent made in 'Third-Party Modules' Directory), and various other config files
Powershell-Tools-Suite - Tooling for Powershell environment. Largely built from scratch, with references from some quality developers it provides world-class support for administration, app development and general functionalities with Github API, Reddit API, etc.