- Enhancement - Terraform Export: Emit lifecycle meta-arguments on resource attributes that do not import correctly to prevent plan from suggesting resource replacement. Currently user_data, user_data_base64 on aws_instance and aws_launch_configuration.
- Enhancement - Employ the exported resource/attribute schema from
terraform-provider-awsto correctly determine which attributes from the state file should be serialized to HCL. - Enhancement - Replace community zip provider with hashicorp/archive for creation of lambda zip files.
- Enhancement - Terraform Export now pulls nested stacks as Terraform modules.
- Fix - Bump dependencies again due to another occurrence of the issue below on a different part of the template.
- Fix - Exception thrown on creating new stack with nested stacks. Issue link
- Enhancement - Use new CloudFormation Parser
- Enhancement - Support AWS.Tools 4.1.16.0
- Enhancement - Rewrite Terraform Export to be a lot smarter due to now being able to fully parse CloudFormation.
- Fix - BucketName is a required property and must be set before making this call. Issue link
- Fix - Resizing vewport throws exception when running on a build agent.
- Fix - ...value of argument "maxLength" is out of range. Issue link
- Fix - Negative MinValue constraint on numeric parameter not working. Issue link
- Enhancement - Experimental release of Terraform Exporter. Issue link
- Fix - Unlabeled graph edges for changes to CreationPolicy, UpdatePolicy, Metadata. Issue link
- Enhancement - Display changeset time as UTC instead of ISO 8601. Issue link
- Fix - Handle Sequence contains no matching element when rendering SVG. Issue link
- Enhancement - Add graphical representation of changeset to browser view. Issue link
- Fix - Python lambda checker. Does not handle type hints in handler function. Issue link
- Fix - Incorrect handling of DisableRollback parameter (package update) Issue link
- Enhancement - Show modification scopes in changeset detail. Issue link
- Fix - Exception when RDS delete creates a snapshot. Issue link
- Enhancement - Link with SourceLink enabled vesions of my own dependencies. No functional change. Issue link
- Enhancement - Add support for Python dependency resolution in lambda packager using
requirements.txt. Issue link
- Fix - Null ref in New-PSCFNChangeset if no changes detected. Issue link
- Enhancement - Add argument completer for
-Select. Issue link - Fix - Session credentials not being picked up (introduced in 4.1.6.7). Issue link
- Enhancement - Dump loaded AWS Assemblies in exception handler with
-Debug. Issue link
- Tech/Enhancement - Remove dependency on
AWS.Tools.Commonthus removing the restriction that the module may only run with a specific vesion ofAWS.Tools. Issue link
- Enhancement - Add new cmdlet
New-PSCFNChangeset. Add mechanism to get detailed changeset information and view in browser, save to file or output to pipeline. Issue link
- Fix - Lambda handler detection fails if handler contains additional arguments (Python). Issue link
- Enhancement - Add
-Selectparameter to stack modification cmdlets. Issue link
- Enhancement - ROLLBACK operations should be in red. issue link
- Fix - Parameters with SSM types should be included on command line. issue link
- Fix - Error message is unhelpful when stack requires capabilities. Issue link
- Technical - Update to AWS.Tools 4.1.6.0
- Enhancement - Support IncludeNestedStacks for changeset geneeration. Issue link
- Fix - Stack update/delete should proceed even when "broken". Issue link
- Enhancement - Mechanism to cancel stack update. Issue link
- Fix - Incorporate Firefly.CloudFormation issue 4
- Fix - Reinstate broken
-UsePreviousTemplateargument. Issue link
- Technical - Upgrade to AWS.Tools v4.1.2.0 and align PSCloudFormation version with AWS Tools dependency
- Enhancement - Verify lambda handlers where possible. Issue link.
- Enhancement - Create a documentation site. Issue link.
- Fix - Python venv support not correct in Linux. Issue link.
- Enhancement - Automatic packaging of templates that contain resources that require packaging, e.g. nested templates, lambdas with local filesystem references to code etc. Issue link.
- Fix - Incorrect error message when a template file is not found. Issue link.
- Fix - Python packager should gather dependencies that are a single file rather than module direcory, e.g.
six. Issue link.
- Fix - Deleting SAM template stack that fails to create throws exception. Issue link.
- Fix - On running stack update, if there are no resources changed, e.g. only outputs have been changed, then exception is thrown. Issue link.
- Fix - Incorrect generation of temporary directory name when packaging single file python lambda with dependencies. Masked until previous bug was fixed.
- Fix - Inverse logic in packaging for single file lambda without dependencies was causing a changed lambda to not be uploaded.
- Fix - Null reference exception when no template provided
- Fix - Python lambda packager with dependencies always uploading new version of package even when nothing has changed.
- Enhancement. Create a mechanism for packaging lambda dependencies. Issue link.
- Fix: Packager is not checking whether packaged resource properties are required by CloudFomation and is incorrectly treating all as required. Issue link.
- Fix -ForceS3. Setting not being passed to Firefly.CloudFormation. Issue link.
- Fix exception thrown when Delete Stack is cancelled
- Bump version of Firefly.CloudFormation for this fix:
- Address potential race condition when monitoring stack events during creation of set of nested stacks. It seems it's possible to retrieve a nested stack resource prior to it being assigned a physical resource ID.
- Packager should not zip a local artifact that is already zipped.
- Complete rewrite in C#
- Support for all CloudFormation properties
- Better authentication handling
- Some breaking changes - see README
This version is a complete re-write in C#. I found that it was becoming a cumbersome beast keeping it in pure PowerShell, taking longer to load the module, and certain parts of it were running quite slowly.
Turning it into a binary module addresses the above problems and reduces complexity given the cmdlets share many common arguments meaning that inheritance can be used to reduce code duplication. It also gives me the chance to showcase three of my other projects: Firefly.CloudFormation which underpins this module, PSDynamicParameters which is a library for managing PowerShell Dynamic Parameters for C# cmdlets and CrossPlatformZip which creates zip files targeting Windows or Linux/Unix/MacOS from any source platform - needed for the packaging component of this module. Lambda does not like zip files that don't contain Unix permission attributes!
- Minimum requirement Windows PowerShell 5.1. All PowerShell Core versions are supported.
- Requires modular AWS.Tools - currently version
4.1.6.0or higher. Monolithic AWSPowerShell is no longer supported (since PSCloudFormation v3.x). Future releases of this module will be version number aligned with the required version ofAWS.Toolsas and when enhancements are added in the space occupied by these cmdlets. - Meaning of
-Waitparameter has changed. This only applies toUpdate-PSCFNStackand means that update should not begin if at the time the cmdlet is called, the target stack is found to be being updated by another process. In this case the update will wait for the other update to complete. All PSCloudFormation cmdlets will wait for their own operation to run to completion unless-PassThruis present. - Return type from the cmdlets has changed. Instead of being just a stack status or an ARN, it is a structure containing both, defined here.
- More use of colour in changeset and stack event display.
- All properties of create, update and delete stack are now supported.
- More complete support for determining AWS credentials from all sources.
- Resource Import supported (since v3.x).
- Dependency Packaging - For script based lambdas, it is possible to package dependent modules directly.
- Support for Python lambda dependency resultion via
requirements.txt - Nested Changeset support - With caveats! See documentation.
- Changeset Detail view - View changeset detail in browser.
Due to the fact that the entire PowerShell process is a single .NET AppDomain, it is possible to fall into DLL hell. This module has various dependencies such as YamlDotNet. If something else in the current PowerShell session has loaded a different version of a dependent library like YamlDotNet, then you will get an assembly version clash when importing this module and the import will fail. Start a new PowerShell session and import there.
There is a way round this for pure .NET Core applications, but then I would have to target PowerShell Core only. The time isn't right for that yet, but if there's sufficient interest, then that could be the v5 release.
- Support for Resource Import
- Use modular AWS.Tools
- One module for Windows PowerShell and PowerShell Core
- Fix bug in nested stack packaging introduced by change in arguments to
New-PSCFNPackage
- Automatically remove temporary template files created by
New-PSCFNPackagewhen piped to stack modification cmdlets
- Add support for SAM templates - basically by adding support for CAPABILITY_AUTO_EXPAND.
- Fix a bug in
New-PSCFNPackagewhere CodeUri entity incorrectly defined forAWS::Serverless::Function - Enhance
New-PSCFNPackageso that a packaged template may be piped directly to the stack modification cmdlets (with caveats - see notes on each cmdlet).
- Fix a pipeline leak in the code that waits for and reports progress causing failure detection to break
- All stack modification operations when run with
-Waitnow return the final status of the stack, e.g.CREATE_COMPLETEor the special valueNO_CHANGEif updating and no change was detected. If an operation fails, then an exception is thrown with propertiesArnandStatusdescribing the stack and the final state. If-PassThruis set along with-Waitthen the arn is returned on success.
- Adds support for stack refactoring - IMPORT operation. Requires AWSPowerShell >= 4.0.1.0 to work.
- Rearrange project structure.
- New cmdlet
New-PSCFNPackage. Packages local artifacts to S3 as peraws cloudformation package - Change all S3 bucket URLs to virtual host style
- Major workover to the tests.
- Minor bug fixes on
Reset-PSCFNStack
- Make
Remove-PSCFNStackask unless-Forceparameter present - Give
Get-PSCFNStackOutputsa-AsHashtableparameter to return the outputs as a raw format for processing by other commands.
10 May 2019
- Fix
Update-PSCFNStackbug where new version of template has fewer template parameters than existing stack.
04 May 2019
- Add
-BackupTemplateswitch toUpdate-PSCFNStackandRemove-PSCFNStack. This saves the current state of the template and any paramaters to files in the current directory. - Fix a bug unearthed with handling of
-ParameterFilewhen testing the above.
01 May 2019
- Add tags to existing cloudformation bucket if they are not present
28 Apr 2019
Update-PSCFNStackshould name the stack when asking to proceed with update- Tag S3 bucket when creating. When PSCloudFormation creates a bucket for processing large templates, it is tagged with info identifying its purpose.
- Support -EndpointUrl so that limited testing with localstack is possible. Add localstack tests.
24 Apr 2019
Update-PSCFNStack- Don't throw if no changes detected. Only warn.Update-PSCFNStack- Don't throw if update cancelled. Only warn.- Oversize templates - Generate a more unique S3 key.
23 Apr 2019
- Fixed issues with powershell-yaml in NetCore/Linux. YAML support now available
16 Apr 2019
- Handle the case where the shell has no AWS region default. This was causing exceptions to be thrown that did not really indicate what the issue was. Now the execption message more accurately identifies the issue with suggestions to correct the problem.
- Add this release notes file.
- Correct license link in manifest.
- Link this file in manifest.
14 Apr 2019
Add a new .NetCore target to provide additional PSGallery package 'PSCloudFormation.netcore` - Now supports PowerShell Core/Linux.
10 Apr 2019
- Improve format of stack event output and fix
SubStringbug inWrite-PSObject - Fix event timestamp bug. PowerShell API returns local times not UTC.
- Add
-ParameterFileargument to support passing of stack parameters in a JSON file.
Log all cloudformation events to console (not only failures), including events from nested stacks. Use colour to indicate different states.
11 Mar 2019
Fixed a bug where the bucket name generated for pushing oversize templates to was not globally unique.
9 Mar 2019
Bugs and enhancements
- Handle large templates : bug
- Wait for rollback if update fails : bug
- Changeset should show resource action : enhancement
Update-PSCFNStacknot detecting newly added stack parameter : bug
9 Oct 2018
This release forwards the rest of the relevant command line arguments of New-CFNStack and Update-CFNStack, a notable omission being -UsePreviousTemplate.
25 Sep 2018
First release.