CAPI 1.168.0

⚠️ Regressions ⚠️

• This capi-release contains a db migration which may fail if there are dependent deployment processes (ForeignKeyViolation). Further details can be found in #3592 & #3538. This issue is fixed with PR (#3596). The PR is integrated in capi-release >= v1.169.0. If you want to be on the safe side, you should skip this version of cf-deployment and use a later version with the fixed migration.

Highlights

CC API Version: 2.219.0 and 3.154.0

Service Broker API Version: 2.15

CAPI Release

• Make CCNG healthcheck script tolerate nginx unavailability #365
• Support Content-Digest header in cc-uploader #31

Bump golang.org/x/crypto from 0.14.0 to 0.17.0

Cloud Controller

• Make user lookup resilient and consistent #3529
• Enhance /v3/organizations/:guid/usage_summary. #3513 The endpoint now additionally shows the following information:
  • total_routes
  • total_service_instances
  • total_reserved_ports
  • total_domains
  • per_app_tasks
  • total_service_keys
• Bump default key length to 2048 and change fingerprint to SHA1 #3555
• Remove DEGENERATE status from deployments #3538
• Use xxHash in Rate Limiter #3557
• Support Content-Digest header in StagingsController #3558
• Align Annotations Key Column with Labels #3401
• Put binding and job creation in one transaction #3567
• Fix migrate failures on vms with missing spec folder #3581

Dependencies:

bump oj from 3.16.2 to 3.16.3
bump hashdiff from 1.0.1 to 1.1.0
bump net-ssh from 7.2.0 to 7.2.1
bump fluent-logger from 0.9.0 to 0.9.1
bump nokogiri from 1.15.5 to 1.16.0 (#3575)
bump sinatra-contrib and sinatra
bump mime-types from 3.5.1 to 3.5.2
bump puma from 6.4.0 to 6.4.1

Cloud Controller Database Migrations

• 20231205143526_remove_deployments_with_degenerate.rb
• 20231221123000_rename_annotations_key_column.rb

Pull Requests and Issues