PSGSuite v2.22.0

Changelog

2.22.0

• Miscellaneous: Config management and portability updates
  • Added: Export-PSGSuiteConfig function to export key parts of your config in a transportable JSON file.
  • Added: Import-PSGSuiteConfig function to import a config from a JSON file (i.e. one created with Export-PSGSuiteConfig) or from a JSON string (i.e. stored in a secure variable in a CI/CD system.)
  • Updated: All config functions now store the P12Key or the ClientSecrets JSON string in the encrypted config directly. This is to allow removal of the secrets files as well as enable PSGSuite to run in a contained environment via importing the config from a secure JSON string.
  • Updated: [Get|Set|Switch]-PSGSuiteConfig to include the P12Key and ClientSecrets parameters that enable housing of the key/secret directly on the encrypted config.
  • Updated: If the global PSGSuite variable $global:PSGSuite exists during module import, it will default to using that as it's configuration, otherwise it will import the default config if set.

---

Instructions

IMPORTANT: You MUST have the module 'Configuration' installed as a prerequisite! Installing the module from the repo source or the release page does not automatically install dependencies!!

1. Click here to download the PSGSuite.zip file attached to the release.
2. If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.

   This is to prevent having to unblock each file individually after unzipping.

3. Unzip the archive.
4. (Optional) Place the module folder somewhere in your PSModulePath.

   You can view the paths listed by running the environment variable $env:PSModulePath

5. Import the module, using the full path to the PSD1 file in place of PSGSuite if the unzipped module folder is not in your PSModulePath:

   # In $env:PSModulePath
   Import-Module PSGSuite
   
   # Otherwise, provide the path to the manifest:
   Import-Module -Path C:\MyPSModules\PSGSuite\2.22.0\PSGSuite.psd1