VaporShell v2.9.1

Changelog

2.9.1 - 2019-09-09

• Issue #61 -- Thanks, @ScriptAutomate!
  • Updated Synopsis and Description for all Resource Type and Property Type functions to include the information from the parsed documentation.

---

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.9.1\VaporShell.psd1

VaporShell v2.9.0

Changelog

2.9.0 - 2019-09-08

• Issue #61 -- Thanks, @ScriptAutomate!
  • Updated Parameter help for all Resource Type and Property Type functions to include the Parameter descriptions.
• Issue #62 -- Thanks, @ScriptAutomate!
  • Updated the CI build process to check all spec sheets for any Resource Types and Property Types that may be missing from us-east-1.
• 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.9.0\VaporShell.psd1

VaporShell v2.8.1

Changelog

2.8.1 - 2019-08-24

• Miscellaneous
  • Updated Package name casing on the PowerShell Gallery from Vaporshell to VaporShell to fix module importing on Linux.
  • 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.1\VaporShell.psd1

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

VaporShell v2.7.3

Changelog

2.7.3 - 2019-04-16

• 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.7.3\VaporShell.psd1

VaporShell v2.7.2

Changelog

2.7.2 - 2019-04-16

• Issue #53
  • Fixed: New-VaporMetadata now allows colons : in the LogicalId.
• Miscellaneous
  • Brought Resource Type and Property Type functions up to current spec sheet.
  • Removed automatic inclusion of AWSTemplateFormatVersion from templates created with Initialize-VaporShell.
  • Set Description parameter as Position

---

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.7.2\VaporShell.psd1

VaporShell v2.7.1

Changelog

2.7.1 - 2019-03-09

• Miscellaneous
  • Brought Resource Type and Property Type functions up to current spec sheet.
  • Fixed: Bug in New-VSStack introduced in v2.7.0. Initial check if stack exists was in a ry block, followed by the call to New-VSChangeSet if so. If New-VSChangeSet fails (i.e. missing Capabilities), it would break out of the ry block and then try to create the stack new. Since the stack does actually exist in this scenario, that throws an expected Stack Exists error and hides the actual error coming from New-VSChangeSet.
  • Added: Add-PolicyAction helper function to enable tab-completion for IAM policy actions, i.e. clouddirectory:RemoveFacetFromObject or organizations:ListHandshakesForAccount
  • Added: Examples folder in-repo to house any example scripts.

---

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.7.1\VaporShell.psd1

VaporShell v2.7.0

Changelog

2.7.0 - 2019-03-08

• Issue #48
  • Fixed: Export-VaporShell was having various failures due to the Format-Json private function called during JSON conversion.
• Miscellaneous
  • Brought Resource Type and Property Type functions up to current spec sheet.
  • Added: Watch and Force parameters to New-VSStack and New-VSChangeSet to watch and/or force stack creation.
  • Added: Watch parameter to Remove-VSStack and Invoke-VSChangeSetExecution to watch stack events.
  • Updated: Watch-Stack to handle multiple stack watching at once.

---

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.7.0\VaporShell.psd1

VaporShell v2.6.3

Changelog

2.6.3

• Issue #44
  • Fixed: Resource from the DSL module was no longer resolving the available types after the CI/CD pipeline switched to compiling the module into a single PSM1 before deploying to the PowerShell Gallery.
• 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.6.3\VaporShell.psd1

VaporShell v2.6.2

Changelog

2.6.2

• Issue #41
  • Fixed: Update-VSStack and Update-VSStackSet were removing the BuiltWith = VaporShell tags if not explicitly included when updating Tags.
• 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:
   Import-Module -Path C:\MyPSModules\VaporShell\2.6.2\VaporShell.psd1