-
Notifications
You must be signed in to change notification settings - Fork 31
v203
dieucao edited this page Mar 13, 2015
·
13 revisions
The cf-release v203 was released on March 12, 2015
- Update to Java Buildpack 2.7.1 details release
- Work continues on support for Asynchronous Service Instance Operations details
- cloudfoundry/cf-release #632: TCP tuning details
- [Experimental] Work continues on /v3 and Application Process Types details
- [Experimental] Initial work on route api merged into cf-release details
- [Experimental] Custom CA Certificates can be added to the trust store on vms in cf-release details
- gorouter can now be configured to terminate ssl details
- manifest changes:
- Moved configuration of lucid64 stack out of a database migration and into manifest configuration details
- For brand new cf deployments, if
cc.stacksis specified in the manifest, then only those stacks specified will be added to the database. - If
cc.stacksis not specified in the manifest, the default set of stacks will be added, currently lucid64 and cflinuxfs2. - For existing deployments, stacks specified in the manifest will be upserted.
- For brand new cf deployments, if
- Add content-type to blobstore file creation details
- cloudfoundry/cf-release #627: Adding X-Forwarded-Proto header to HTTP check for UAA and Login details
- As a CF operator, I can specify the default stack in the manifest details
- Fixed a bug when an app has a lot of fingerprints matched during resource matching, it should still be able to stage details
- As a cf operator I can specify via manifest "min_cli_version" and "min_recommended_cli_version" for /v2/info details
- Rescue warden client disconnect when doing varz updates details
- Security Groups applied to the space are visible to non-admins with correct permissions details
- cloudfoundry/cf-release #623: Enable explicit configuration of uaa.issuer details
- Placeholder details
- BOSH Version: 148
- Stemcell Version: 2859
- CC Api Version: 2.23.0
- No need to ask permission - if you want to make an edit or add a new section, just do it!
- The official cf-docs maintainers cherry-pick content from this wiki for the official docs
- The contents of this wiki are in no way endorsed, maintained or supported by the core Cloud Foundry team
- Development Process
- Mailing Lists & Chats
- CI and the Commit Pipeline
- Contributing Code or Docs
- Contribution Standards
- Design Documents
- Proposing New Features
- Adding New Services
- Project Incubator
- Reporting Security Vulnerabilities
- CFF vulnerability mgt
- CAB meeting minutes
See CFF official project list.
Roadmaps are reflected in pivotal trackers. Tracker Instructions and steps to watch stories. Here is a flat list of all trackers:
- BOSH
- BBR
- CF Abacus
- CF App Autoscaler
- CF Buildpacks
- Concourse roadmap, and milestones
- CF Containerization/quarks
- CF Container Networking
- CF CAPI
- CF API K8s Evolution
- CredHub
- CF CLI
- CF CLI V3 acceleration
- CF Diego
- CF Docs
- CF Eclipse
- CF Eirini
- CF Flintstone
- CF Foundation
- CF Garden
- CF Greenhouse (windows)
- CF GrootFS (aka Garden RootFs)
- CF Identity (aka UAA)
- CF Infrastructure (incls BBL)
- CF Java Buildpack
- CF Java Client
- CF Lattice
- CF Logging and Metrics
- CF MEGA (Release Integration)
- CF Networking - CF K8S
- CF Networking - CFAR Mesh
- CF Mysql (core services)
- CF Notifications
- CF Permissions
- CF Persistence
- CF Postgres-release
- CF Runtime OG
- CF Routing
- CF Routing TCP
- CF services API (aka SAPI)
- Cloud Service Brokers (by SAPI/service enablement team)
- Kubo
- License Finder
- BBR
- Buildpacks
- BOSH
- BOSH CPIs
- Cf Java Client
- Core services (mysql) - repo
- Garden
- Grootfs
- Infra/tools
- Java Buildpack
- Kubo - repo
- Loggregator
- Persistence
- Release integration - repo
- Routing
- Runtime - repo
- Service API (aka SAPI)
Maybe other CIs hosted on cf-app.com are mentioned in slack ?
- See Client Tools on docs
- 3rd Party Compatible Apps