CFT will now read the following properties from the manifest.yml and set them as part of the push operation when deploying or updating an application:
Note that 'health-check-http-endpoint' is only supported on newer Cloud Foundry and must be used with health check type "http".
In addition to reading this property and setting it during deployment of an application, for certain Cloud Foundry servers like Pivotal Web Services and PCF, a user can also specify the stack in the deployment wizard:
If the stack setting is not applicable to a specific branding extension, the adopter can also customize their branding to disable the stack UI via the org.eclipse.cft.server.ui.brandingUI extension point.
CFT now supports application names with '.' separation. Users can now specify dot-separated application names when deploying an application:
All applications, including web applications, can now be deployed to Cloud Foundry without a mapped URL. Although CFT will still suggest a URL in the deployment wizard, users can clear the URL and deploy the application without a URL, similar to the --no-route option in cf CLI push.
Substantially faster refresh of deployed applications in the Cloud Foundry server: the list of applications in a Cloud Foundry server is now refreshed in parallel, substantially improving refresh time when a Cloud Foundry server first connects, or a user manually clicks the refresh button in the Cloud Foundry editor.
Basic support for detecting changes in a manifest.yml and prompting the user to update the changes in Cloud Foundry for deployed applications:
A dialogue opens asking the user to confirm whether the update should occur, and will show the difference between the local manifest.yml file and the existing Cloud values:
This dialogue will open on detected changes when any of the following operations are performed on an already deployed application:
Future versions of CFT may expand this support for other manifest properties as well as top-level properties.