Use BAL on windows2012R2

[sesmith177]

There still needs to be a separate windows_app_lifecycle package to
account for differences betwen 2012R2 and 2016 (i.e diego-sshd /
lifecycle / BAL differences )

• Remove windows_app_lifecycle blob
• Add tar blob
• Compile BAL for windows2012R2 and install the correct versions of
  diego-sshd.exe and lifecycle.exe

[#151173124]

Signed-off-by: Sunjay Bhatia [email protected]

[cfdreddbot]

Hey sesmith177!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/151229417

The labels on this github issue will be updated when the story is started.

[sesmith177]

Note that this PR depends on cloudfoundry/buildpackapplifecycle#27 having been merged

[emalm]

Thanks, @sesmith177! Prioritizing for the Diego team to evaluate, blocked on https://www.pivotaltracker.com/story/show/151227754. I assume the windows_app_lifecycle package also needs to stick around indefinitely to prevent breaking LRPs for Windows apps that download it as an asset.

Best,
Eric

[sunjayBhatia]

@emalm yeah, if we were to get rid of the WAL and CAPI were configured with the BAL instead, users would have to restage all their apps because the WAL blob would have been removed from the file server

[emalm]

Sounds good, @sunjayBhatia. I think a restart would suffice, so once Diego allows LRP rolling updates CC could eventually migrate all the legacy Windows LRPs to a BAL-based definition seamlessly. But that's a special case of CC using that mechanism to "update" URLs for assets in general, including also droplets.

[emalm]

Merged via bc27e56.