VaporShell v2.8.0

Changelog

2.8.0 - 2019-08-08

• Issue #57
  • Fixed: ProcessRequest4 private function will now use the Async methods if detected, so usage of the AWSPowerShell.NetCore or AWS.Tools.* modules from Windows PowerShell will still work as expected when using any of the SDK wrapper functions like Watch-Stack
• Miscellaneous
  • Brought Resource Type and Property Type functions up to current spec sheet.

---

Instructions

1. Click here to download the VaporShell.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 VaporShell if the unzipped module folder is not in your PSModulePath:

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