- 2.13.0 - 2020-07-30
- 2.12.2 - 2020-06-04
- 2.12.1 - 2020-05-05
- 2.12.0 - 2020-05-03
- 2.11.1 - 2020-03-09
- 2.11.0 - 2020-03-04
- 2.10.1 - 2020-02-20
- 2.10.0 - 2020-02-18
- 2.9.5 - 2020-02-17
- 2.9.4 - 2019-12-11
- 2.9.3 - 2019-11-24
- 2.9.2 - 2019-10-06
- 2.9.1 - 2019-09-09
- 2.9.0 - 2019-09-08
- 2.8.1 - 2019-08-24
- 2.8.0 - 2019-08-08
- 2.7.3 - 2019-04-16
- 2.7.2 - 2019-04-16
- 2.7.1 - 2019-03-09
- 2.7.0 - 2019-03-08
- 2.6.3
- 2.6.2
- 2.6.1
- 2.6.0
- 2.5.5
- 2.5.4
- 2.5.3
- 2.5.2
- 2.5.1
- 2.5.0
- 2.4.1
- 2.4.0
- 2.3.0
- 2.2.1
- 2.2.0
- 2.1.2
- 2.1.1
- 2.1.0
- 2.0.3
- 2.0.0
- 1.2.3
- 1.2.2
- 1.2.0
- 1.1.5
- 1.1.0
- 1.0.0
- 0.7.10
- 0.7.09
- 0.7.08
- 0.7.07
- 0.7.06
- 0.7.05
- 0.7.04
- 0.7.03
- 0.7.02
- Issue #81
- Fixed:
Add-ConIf
parameter error message. - Fixed:
Add-ConIf
now allows boolean values.
- Fixed:
- Issue #82
- Fixed: Condition Functions are now supported on any parameter that already accepts Intrinsic Functions.
- Miscellaneous
- Updated PseudoParameter list to current spec.
- Switched default branch from
master
tomain
.
- Issue #79
- Fixed: Documentation on
New-VaporCondition
- Fixed: Documentation on
- Miscellaneous
- Fixed:
Watch-Stack
colorization bleed on BackgroundColor changes - Fixed:
Watch-Stack
now exits when all stacks are in a stable state, not early if one stack stablizes before the rest.
- Fixed:
- Issue #74
- Fixed:
UpdateReplacePolicy
was incorrectly nested under the Resource Properties, not top-level next toDeletionPolicy
.
- Fixed:
- Issue #75
- Added: Support for
ResourcesToImport
declaration on changes sets withNew-VSChangeSet
- Added: New helper function
Add-VSChangeSetResourceToImport
to create theResourceToImport
object needed as the value of theResourcesToImport
parameter onNew-VSChangeSet
- Added: Support for
- Issue #72
- Updated allowable types for
Add-FnJoin
to match current AWS documentation (was missingFn::ImportValue
andFn::Sub
support)
- Updated allowable types for
- Issue #69 + PR #70 - Thanks, @indented-automation!!!
- Started
VaporShell.Core
class library to include with the module, first class beingTransformTagAttribute
to cleanly convertTags
parameter input to the appropriate format if not already. - Added Pester tests to confirm Tag transforms are working as expected.
- Started
- 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
andAdd-FnTransform
.
- 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 theBegin
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.
- Removed
- Miscellaneous
- 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
- Issue #66
- Fixed:
Int
,Double
, andBoolean
parameters now accept CloudFormation Intrinsic Functions as parameter values.
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Issue #61 -- Thanks, @ScriptAutomate!
- Updated Synopsis and Description for all Resource Type and Property Type functions to include the information from the parsed documentation.
- 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
.
- Updated the CI build process to check all spec sheets for any Resource Types and Property Types that may be missing from
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Miscellaneous
- Updated Package name casing on the PowerShell Gallery from
Vaporshell
toVaporShell
to fix module importing on Linux. - Brought Resource Type and Property Type functions up to current spec sheet.
- Updated Package name casing on the PowerShell Gallery from
- 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 likeWatch-Stack
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Issue #53
- Fixed:
New-VaporMetadata
now allows colons:
in the LogicalId.
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Removed automatic inclusion of
AWSTemplateFormatVersion
from templates created withInitialize-VaporShell
. - Set
Description
parameter as Position0
onInitialize-VaporShell
.
- 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 atry
block, followed by the call toNew-VSChangeSet
if so. IfNew-VSChangeSet
fails (i.e. missing Capabilities), it would break out of thetry
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 fromNew-VSChangeSet
. - Added:
Add-PolicyAction
helper function to enable tab-completion for IAM policy actions, i.e.clouddirectory:RemoveFacetFromObject
ororganizations:ListHandshakesForAccount
- Added: Examples folder in-repo to house any example scripts.
- Issue #48
- Fixed:
Export-VaporShell
was having various failures due to theFormat-Json
private function called during JSON conversion.
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Added:
Watch
andForce
parameters toNew-VSStack
andNew-VSChangeSet
to watch and/or force stack creation. - Added:
Watch
parameter toRemove-VSStack
andInvoke-VSChangeSetExecution
to watch stack events. - Updated:
Watch-Stack
to handle multiple stack watching at once.
- 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.
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Issue #41
- Fixed:
Update-VSStack
andUpdate-VSStackSet
were removing theBuiltWith = VaporShell
tags if not explicitly included when updating Tags.
- Fixed:
- Miscellaneous
- Brought Resource Type and Property Type functions up to current spec sheet.
- Issue #41
- Fixed:
Tags
parameter on the following functions was incorrectly expectingString
values, switched toHashtable
:New-VSStack
Update-VSStack
New-VSStackSet
Update-VSStackSet
New-VSChangeSet
- Fixed:
- Fixed:
Watch-Stack
was not closing when stack was in a COMPLETE or FAILED status. - Updated: Build and deploy process to funnel everything through Azure Pipelines
- Fixed
Add-UserData
's use ofFn::Join
so that it automatically sets\n
as the delimiter with the-UseJoin
parameter - Updated Resource Type and Property Type functions to latest CloudFormation spec
- Updated
Add-UserData
with-Persist
switch to allow flagging the UserData as persistent by adding the<persist>true</persist>
tag on the bottom of the contents. - Updated all Resource Property Type functions to include Verbose output of the resulting JSON object
- Updated
Add-VSLambdaFunctionCode
with-ZipFilePath
parameter to enable passing of a file path instead of reading ZipFile as string only
- Fixed bug in
Watch-Stack
updates found in v2.5.2
- Updated
Watch-Stack
to format the table based on each column's data width so headers aren't readded
- Updated script methods on
Initialize-VaporShell
andImport-VaporShell
- Updated
Add-UserData
with new-UseJoin
parameter to add UserData using Fn::Join for readability if preferred and-Replace
to supply a hashtable of values to replace in your UserData with script values - Updated overall performance in
Add-UserData
- Added
Import-VSTemplateConfig
to enable external template usage for dynamic templates
- Added
Vaporshell.Condition
to the acceptible types for standard resource parameters (Issue #35)
- Added
ToString()
method override toNew-VaporResource
for convenience during template building Issue #34
- Added DSL wrapper to allow a different style of template building
- Added short aliases for all Condition and Intrinsic functions
- Removed private function Import-AWSSDK and added SDK import to PSM1
- Fixed issue #25 by updating
Convert-SpecToFunction
to exclude common parameters from being added as properties to outputted resource and resource property objects
- Updated Travis-CI tests to use latest PowerShell release
- Updated AppVeyor tests to test in both PowerShell Core and Windows PowerShell
- Updated resource types/property types to latest spec sheet
- Renamed New-VSS3Bucket to New-VSS3Box to prevent duplicate function name collision
- Added additional ConEmu support to
Watch-Stack
- Updated Colorize to match against ROLLBACK events
- Updated resource and property types, adding another 107 functions to the module
- Updated
Watch-Stack
for ConEmu users so that it will create a new tab in ConEmu with the-InNewWindow
parameter instead of launching a PowerShell.exe window
- Added
ToJSON()
,ToYAML()
methods to Template object to allow quick conversion to either format - Added
ToString()
method to Template object to output to JSON string to pass the template object directly to-TemplateBody
parameters when creating stacks/change sets
- Completely wrapped the AWS .NET SDK's CloudFormation model, allowing for full stack / change set / stack set management from VaporShell
- Fixed Export-VaporShell to work with PowerShell v3 and v4 (Issue #15)
- Added native template validation via the AWS .NET SDK (core and 45)
- Updated module manifest description for PSGallery
- Updated Resource and Property Types to include new entries from AWS Specifications
- Updated Convert-SpecToFunction to clean up bool attribute addition (intermittent conversion from bool to string) and also leverage $PSBoundParameters (slight speed and cleanliness boost)
- Restored Coveralls coverage in Pester tests
- Adjusted Export-VaporShell -ValidateTemplate to use file:// for the templateBody vs fileb:// (errors during Travis tests on Linux)
- Fixed default PowerShell JSON output formatting when using ConvertTo-Json; default formatting caused a large template to exceed CloudFormation's limits due to the extra spacing. Added in the private function
Format-Json
and set the default output to be cleaned up inExport-VaporShell
- Added
Update-VSResourceFunctions
- Updated all Resource and Property Type functions
- Added full YAML support for import and export via leveraging
cfn-flip
from awslabs - All functional issues resolved, ready to declare v1!
- Added full Serverless coverage
- Expanded
Add-UserData
functionality to detect ps1, bat & cmd files and tag them if needed
- Fixed issue where List parameters with single values were being cast as a single string/object instead of an array with a single string/object
- Added
-ValidateTemplate
parameter to leverageaws cloudformation validate-template
for syntax validation
- AppVeyor config updates
- Added in FunctionBuilder and finished building all resource and resource property types
- Added
Add-UserData
- Added Coveralls.io code coverage grading to CI process
- Expanded AppVeyor tests
- Updated module minor version to 7