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 onwards, 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 have -s windows2016 as a deprecated stack name, requiring developers and operators to use the -s windows stack name. **PASW 2.8 onwards, you should update any apps using the windows2016 stack, to use the windows stack. **
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.
Migrating your apps to the windows stack
- Find out which apps on your foundation are using the
-s windows2016stack name, by using Stack Auditorcf audit-stackcommand - Use the Stack Auditor
cf change-stackcommand to update all apps to use thewindowsstack - Update all app manifests and pipeline to specify the
windowsstack
Links & Resources
- Download Buildpack Extensions (contains Stack Auditor)
- PAS Windows 2.4 release notes introducing
windowsstack - PAS Windows 2.5 release notes deprecating
windows2016stack - Documentation on how to use the Stack Auditor plugin
