Pivotal Engineering Journal

Technical articles from Pivotal engineers.

Ensure Windows apps are using the `windows` stack before upgrading to PASW 2.8

Pivotal Application Service for Windows introduced the -s windows stack name in PASW 2.4, reducing the operator and developer need to concern themselves with specific Windows Server versions. From PASW 2.4 thru PASW 2.7, both the windows2016 and windows stack names worked - giving sufficient time to migrate apps over to the new stack name.

Posted on by
Categories:   PASW    .NET    Windows    stack    cf   
Edit this post on GitHub.

Pivotal Application Service for Windows introduced the -s windows stack name in PASW 2.4, reducing the operator and developer need to concern themselves with specific Windows Server versions. From PASW 2.4 thru PASW 2.7, both the windows2016 and windows stack names worked - giving sufficient time to migrate apps over to the new stack name.

Pivotal Application Service for Windows 2.8 will remove support for the deprecated -s windows2016 stack name, requiring developers and operators to use the -s windows stack name. Prior to upgrading to PASW 2.8, you MUST update any apps using the windows2016 stack, to use the windows stack. Apps that are not updated to the windows stack WILL NOT START after upgrading to PASW 2.8.

Operators can use the Stack Auditor CF CLI plugin to get an inventory of all apps and their current stack, in a given foundation. They can also use the plugin to update an app stack to windows without needing access to the app’s source or automation pipeline. Be aware, changing the stack of an app WILL cause the app to restart which may lead to temporary downtime.

The plugin is available for download in the Buildpack Extensions area of PivNet. Watch a video of running stack audit as well as upgrading apps, below.

Mandatory actions before upgrading to PASW 2.8


video of running stack audit as well as upgrading apps