Skip to content
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.

v0.17.0 for PCF 1.7.0
Compare
Choose a tag to compare
@pcfdev-bot pcfdev-bot released this 28 Jun 21:01
· 256 commits to master since this release
v0.17.0
d452eb8

PCF Dev v0.17.0 is an open beta release that is publicly available on the Pivotal Network.
Feedback for the commercial version of PCF Dev may be left in the Github issues for this repository.

Changelog

  • The plugin may be installed or upgraded by running it directly (as well as via cf install-plugin). (#76, #77)

    $ unzip pcfdev-v0.17.0+PCF1.7.0-<OS>.zip
$ ./pcfdev-v0.17.0+PCF1.7.0-<OS>
Plugin successfully upgraded, run: cf dev help
$ cf dev help

  • A corresponding PCF version is now included in the PCF Dev version for more clarity.

  • Whitespace in proxy variables is now ignored. The delimitation of no_proxy may now include spaces. (#82)

  • Apps Manager is now included with PCF Dev. Navigate to http://local.pcfdev.io in your web browser to check it out. (Your browser may warn you that the SSL certificate is self-signed.) (#12, #60)

  • A default non-administrative user is now included: Email: user / Password: pass

  • Application security groups are now open to private IP ranges by default. You may remove the all security group to revert to the previous behavior of only allowing access to public IP ranges. (#80, #81)

  • HTTP/HTTPS proxy domains that resolve to multiple IP addresses are now supported. (#85)

  • Custom OVAs may be used with the CLI plugin via the undocumented -o flag: cf dev start -o custom.ova. This will eventually replace Vagrant for booting OSS builds of PCF Dev. The source code for the CLI plugin will be released soon. (#84)

  • PCF Dev VMs that fail to start may always be destroyed with cf dev destroy. Running cf dev status will report these VMs as "Invalid" and instruct you to destroy them. (#78, #79)

  • The entire PCF Dev VM now lives in the ~/.pcfdev directory.

  • Local network detection is significantly improved.

  • Component versions are still matched to PCF 1.7.0.

  • Experimental support for AWS has been discontinued temporarily. We found that many users had trouble configuring PCF Dev on AWS in a secure and usable manner. AWS support will return soon, and will be available from the AWS Marketplace. If you are a Pivotal employee, please contact us on Slack for continued AWS support.

Elastic Runtime
  • cf-release maintained at v235
  • diego-release maintained at v0.1467.0
  • garden-linux-release maintained at v0.337.0
  • etcd-release maintained at v45
Services
  • cf-mysql-release maintained at v26
  • cf-redis-release maintained at v424.18.0
  • cf-rabbitmq-release maintained at v210.8.0
Tools
  • Apps Manager added using custom build from 6/15/2016.

Known Issues

  • The Apps Manager SSL certificate is self-signed. Your browser may warn you about this when you navigate to https://local.pcfdev.io. This warning can safely be ignored.
  • Support for custom VM IP addresses and domains has been delayed until the next release.
  • Support for running multiple PCF Dev VMs on the same machine will be available soon.

Corresponding OVA Version: 0.136.0

Assets 2
Loading