VaporShell v2.12.0.20200503

Changelog

2.12.0 - 2020-05-03

• Issue #74
  • Fixed: UpdateReplacePolicy was incorrectly nested under the Resource Properties, not top-level next to DeletionPolicy.
• Issue #75
  • Added: Support for ResourcesToImport declaration on changes sets with New-VSChangeSet
  • Added: New helper function Add-VSChangeSetResourceToImport to create the ResourceToImport object needed as the value of the ResourcesToImport parameter on New-VSChangeSet

---

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

VaporShell v2.11.0.20200304

Changelog

2.11.0 - 2020-03-04

• Issue #69 + PR #70 - Thanks, @indented-automation!!!
  • Started VaporShell.Core class library to include with the module, first class being TransformTagAttribute to cleanly convert Tags parameter input to the appropriate format if not already.
  • Added Pester tests to confirm Tag transforms are working as expected.
• Issue #68 - Thanks, @indented-automation and @austoonz!!!
  • Surfaced errors better on AWS SDK errors so the actual error is visible.
  • Added the FallbackCredentialFactory to better support running in environments where credentials files are not a practical option.
• Miscellaneous
  • Updated PseudoParameter list to current spec.
  • Added newer intrinsic functions Add-FnCidr and Add-FnTransform.

---

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

VaporShell v2.10.1.20200226

Changelog

This is a standard scheduled release to bring this module up to the current CloudFormation specification sheet.

2.10.1 - 2020-02-20

• Miscellaneous
  • Removed RequiredAssemblies from the module manifest due to collisions with existing AWS modules.
  • Moved the Assembly import to a private function Import-AWSSDK and added a call to that function in the Begin block of each function wrapping AWS SDK calls.
  • Removed the process that imports the assemblies on module load so they're only imported if needed for SDK wrapper calls.

---

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

VaporShell v2.10.1.20200220

Changelog

2.10.1 - 2020-02-20

• Miscellaneous
  • Removed RequiredAssemblies from the module manifest due to collisions with existing AWS modules.
  • Moved the Assembly import to a private function Import-AWSSDK and added a call to that function in the Begin block of each function wrapping AWS SDK calls.
  • Removed the process that imports the assemblies on module load so they're only imported if needed for SDK wrapper calls.

---

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

VaporShell v2.10.0.20200219

Changelog

2.10.0.20200219 - 2020-02-19 (Scheduled Release)

This is a standard scheduled release to bring this module up to the current CloudFormation specification sheet.

• Miscellaneous
  • Brought Resource Type and Property Type functions up to current spec sheet.

---

Last Changelog Entry

2.10.0.X - 2020-02-18

• Brought minimum .NET version to 4.7.2
• Updated build process to use InvokeBuild instead of psake
• Updated tasks to pull down the latest dependent assemblies during build
• Added scheduled build triggers for weekly deployments
• Changed the version scheme so it includes the date stamp as the build version

---

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

VaporShell v2.10.0.20200218

Changelog

2.10.0.X - 2020-02-18

• Brought minimum .NET version to 4.7.2
• Updated build process to use InvokeBuild instead of psake
• Updated tasks to pull down the latest dependent assemblies during build
• Added scheduled build triggers for weekly deployments
• Changed the version scheme so it includes the date stamp as the build version

---

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

VaporShell v2.9.5

Changelog

2.9.5 - 2020-02-17

• Issue #66
  • Fixed: Int,Double, and Boolean parameters now accept CloudFormation Intrinsic Functions as parameter values.
• 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.5\VaporShell.psd1

VaporShell v2.9.4

Changelog

---

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

VaporShell v2.9.3

Changelog

2.9.3 - 2019-11-24

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

VaporShell v2.9.2

Changelog

2.9.2 - 2019-10-06

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