cloudfoundry/capi-release 1.78.0

CAPI 1.78.0

on GitHub

Highlights

• Logcache requests for container metrics should have retry logic. This mitigates push downtime during logcache upgrades.
• Revisions now have system generated descriptions
• Revisions support custom start commands
• Service brokers can now set polling intervals and maximum polling durations for how often and for how long the platform will poll the broker during an operation
• Cloud Foundry users can now send organization name, space name, and instance name to their service broker providers

CC API Version: 2.133.0 and 3.68.0

Service Broker API Version: 2.14

CAPI Release

Cloud Controller

• API client can create a domain details
• API client can discover a link to the resource match resource
• API client should be able to discover domains on the v3 API details
• API client should be able to list feature flags details
• API client should be able to update a feature flag details
• API client should be able to see the details of a feature flag details
• CLI app dev should see a meaningful error message if they attempt to use health check HTTP and not have the HTTP endpoint set in the manifest details
• Add description when a new revision is created details
• As a CC client, if the bits service is enabled, I can see a link to the bits service API in / details
• As a service author, I can set a polling interval for cf bind-service so that my broker doesn't have to handle unnecessary numbers of requests details
• As a service author, I can set a polling interval for cf create-service so that my broker doesn't have to handle unnecessary numbers of requests details
• As a service author, I can set a polling interval for cf delete-service so that my broker doesn't have to handle unnecessary numbers of requests details
• As a service author, I can set a polling interval for cf unbind-service so that my broker doesn't have to handle unnecessary numbers of requests details
• As a service author, I can set a polling interval for cf update-service so that my broker doesn't have to handle unnecessary numbers of requests details
• As a service author, I see context.organization_name and context.space_name on a bind request from a customer using CF details
• As a service author, I see instance_name, organization_name and space_name in the context object on a provision and update request from a customer using CF details
• As a service author, I want cf bind-service to respect the max polling duration set on the plan level details
• As a service author, I want cf create-service to respect the max polling duration set on the plan level details
• As a service author, I want cf delete-service to respect the max polling duration set on the plan level details
• As a service author, I want cf unbind-service to respect the max polling duration set on the plan level details
• As a service author, I want cf update-service to respect the max polling duration set on the plan level details
• Custom start commands for a process type are part of an app revision details
• Feature Flags are not experimental in the API docs and v3 link details
• Only roll back to a revision with a droplet details
• Remove unfinished v3 domains controller skeleton so that CAPI can release without permissions issues details
• Revisions have a link to their environment variables details
• log cache requests for container metrics should have retry logic details

Cloud Controller Database Migrations

• 20190206191247_add_custom_commands_to_revisions.rb
• 20190219161111_add_maximum_polling_duration_to_service_plans.rb
• 20190220001829_add_encryption_iteration_count_to_apps.rb
• 20190220003558_add_encryption_iteration_count_to_buildpack_lifecycle_buildpacks.rb
• 20190220003646_add_encryption_iteration_count_to_buildpack_lifecycle_data.rb
• 20190220003740_add_encryption_iteration_count_to_droplets.rb
• 20190220003808_add_encryption_iteration_count_to_env_groups.rb
• 20190220003847_add_encryption_iteration_count_to_packages.rb
• 20190220003903_add_encryption_iteration_count_to_revisions.rb
• 20190220003916_add_encryption_iteration_count_to_tasks.rb
• 20190220004407_add_encryption_iteration_count_to_service_bindings.rb
• 20190220004428_add_encryption_iteration_count_to_service_brokers.rb
• 20190220004441_add_encryption_iteration_count_to_service_instances.rb
• 20190220004454_add_encryption_iteration_count_to_service_keys.rb
• 20190221221532_create_revision_process_commands_table.rb
• 20190222004908_remove_revisions_encrypted_commands_by_process_type.rb
• 20190222190051_add_encryption_iteration_count_to_encryption_key_sentinels.rb
• 20190223002950_remove_encryption_iteration_defaults.rb
• 20190302003850_add_revision_description_column.rb

Pull Requests and Issues

• cloudfoundry/cloud_controller_ng #1281: Surprising error when trying to use disabled buildpacks details
• cloudfoundry/cloud_controller_ng #1284: 500 when uploading invalid package bits details
• cloudfoundry/cloud_controller_ng #1293: "enhance this page" link to apidocs website details
• cloudfoundry/cloud_controller_ng #1295: Respect 'retry-after' header for operations on service bindings details
• cloudfoundry/cloud_controller_ng #1296: Respect 'retry-after' header for operations on service instances details