Powerdeploy 1.0.0-beta-9

Force UTF-8 encoding for incoming settings files and other deployment assets

PSON files and application configuration transforms (and other conventions) now support additional characters. PowerShell would read the files properly if they were saved with a BOM, but not UTF-8 is enforced regardless of the file's encoding.

#20

Support additional deployment lifecycle hooks

Scripts can now be registered to execute before, during, and after a number of phases (executed in the following order):

• Prepare
• Install
• Configure

Powerdeploy 1.0.0-beta-8

Bug Fixes

Support install without specifying variables

Variables are not required when calling Install-DeploymentPackage, but
there was a bug that would set the variables to null if they weren't
specified.

Remove unused Install-DeploymentPackage param

The -DeploymentTempRoot parameter was not used after moving Powerdeploy to
v1 but was still a required parameter on the cmdlet.

Powerdeploy 1.0.0-beta-7

Enhancements

Allow pre-processing of configuration variables

When Get-ConfigurationVariable is called with -Resolved, environment settings are merged in with application settings and the original context of the source variable is lost. There are times when it is important to know, in order to extend the configuration mechanism, the detail of the original variable (name, scope, etc.).

The new -ProcessVariable parameter allows a caller to process variables prior to resolving.

Powerdeploy 1.0.0-beta-6

Bug Fixes

Allow registration of multiple scripts

By design, multiple scripts can be registered for each deployment phase,
but the code was wiping out any existing registration any time a new one
was added.

Powerdeploy 1.0.0-beta-5

Bug Fixes

Always return Hashtable in Get-DeploymentVariable

When using Get-DeploymentVariable without a variable name both the
hashtable and a $null value were being returned which resulted in an
object array being returned from the cmdlet, rather than a hashtable.

Enhancements

Rename Settings property of deployment to Variables

The property returns the configuration variables passed into Powerdeploy
and was renamed for consistency.

Powerdeploy 1.0.0-beta-4

• Support additional characters in environment pson filename

Powerdeploy 1.0.0-beta-3

• New configuration structure
• Settings no longer stored to disk on remote
• Post install script
• Remote errors handled better