Release 1.2.1 With the release of cf-puppeteer 1.2.0 we just fixed some bugs that introduces in the version 1.2.0. Feedback Please give some feedback and open a issues if you find one. github-issue tracker Changelog Changed 🛠 add more trace logging make tests more stable Fixed 🐛 find matching routes pss a vars file combined with ‘legacy-push’ Github Issues 🐙 To get some more insides about the changes / fixes, you can see all the github issues that are part of the new version.

Release 1.2.0 With the release of cf-puppeteer 1.2.0 we just fixed some bugs and bring some droped features back. Feedback Please give some feedback and open a issues if you find one. github-issue tracker Changelog Features 🚀 --vars-file argument was available again, so it’s possible to use manifest files with placeholderst Changed 🛠 All routes will be switched lazy (after starting up the new application) Dropped CF_PUPPETEER_TRACE and replace them with CF_TRACE (read the README “Known issues section” for using it) Fixed 🐛 Error while passing environment variables on legacy push (–env) Typos, error messages Download: Github

Release 1.1.3 With the release of cf-puppeteer 1.1.3 we just fixed and improve some small but important things. Feedback Please give some feedback and open a issues if you find one. github-issue tracker Changelog Changed 🛠 Improve logging Add error message for manifest path declarative (when the path contains a wildcard) Fixed 🐛 Venerable application will be deleted correct after pushing a application Typos, error messages Download: Github

Release 1.1.2 With the release of cf-puppeteer 1.1.2 we worked on backporting some v3 features to the legacy-push option. We also implemented the possibility to use all features with docker images. All new features and bugfixes are listed below. New Legacy-push options: --route-only --no-route New v3 options: --docker-image --docker-username Feedback Please give some feedback and open a issues if you find one. github-issue tracker Changelog Changed 🛠 refactor environment parsing cleanup code update documentation back port “–no-route” and “–route-only” option to “–legacy-push” (v2).

Release 1.1.1 With the release of cf-puppeteer 1.1.1 we worked on some feedback of the community and make the usability easier and more user friendly All new features and bugfixes are listed below. --no-route --venerable-action Examples No-routes Deploy the application without route switching - old application should still run and new one should be stoped after deployment. (Venerable-action will be set to none automatically ) cf zero-downtime-push -f ./manifest.yml --no-routes now you can add new services or what ever you want.

Release 1.1.0 With the release of cf-puppeteer version 1.1.0 we bring some new features and bugfixes. The new features and bugfixes are listed below. --no-route --route-only Examples No-routes Deploy the application without route switching - old application should still run and new one should be stoped after deployment cf zero-downtime-push -f ./manifest.yml --no-route --vendor-option none right now you can add new services or what ever you want. To start the new application with routes and cleanup the old one you can do the following things:

Release 1.0.0 - Final release is here With the first final release we bring the version 1.0.0 to cf-puppeteer. We bring some small features, many bug fixes and a complete refactoring of the old version of cf-puppeterr. Right now it’s possible to choose between an v2 or v3 cf push of your application. CF-Puppeteer checks the cf-controller version and use the v3 push if it’s possible. To use the old push manually you can pass the option: --legacy-push

Release 1.0.0-rc.0 - First release candiate With the first rc we dont bring “new” features!, we just pushed the deployment on the newest level of cf api’s. The new version now supports the newest structure of cf-manifests.yml files. The plugin is also a “complete” rewrite of the older versions. For the new rc versions we will focus on bringing docker support, adding more tests and clean / simplify the plugin implementation.

Release 0.0.14 brings just small bug fixes and one new feature Changelog Added health check settings (v3): fallback on app manifest for health-check-type and health-check-http-endpoint settings print more information on Cloud Foundry API calls (if env CF_PUPPETEER_TRACE = true) Fixed health check settings (v3): support for applications with empty command go linting issues Changed improve documentation Specials Special thanks to the first contributor to cf-puppeteer plugin Skyfalke

Release 0.0.13 was a big feature and bugfix release. With the new release we will start with focus to bring the first Verion 1.0.0 to our customers. With the release we changed following things Changelog Added add -vendor-option to stop old service instead of deletion add –health-check v3 command to specify a invocationtime for health checks Changed cleanup manifest parser update documentation Fixed env arg issue when passing key value pairs argument handling Specials Special thanks to the first contributor to cf-puppeteer plugin Skyfalke

Release 0.0.12 was a feature and bugfix release. With the release we changed following things Changelog Added add -env argument to pass environment variables Changed Change buildscript to generate sha1 sums for each file Fixed timeout issue with specified timout at manifest (before -t worked only) documentation Download: Github

New new release verion of cf-puppeteer was just a rename because a naming confict of cf-plugins Issue Download: Github