Open DanFrei opened 2 months ago
@DanFrei The best way to test will be to cloning spring-cloud-deployer, bumping CF Java Client to 5.12.2.RELEASE and doing a snapshot build and then doing snapshot builds of scdf 2.11.x and trying the cf-local use of dataflow server and skipper.
Hello @corneil Thank you for your reply! Perhaps I'm missing something but when you say "the best way to test" - what do you refer to? Currently we know for sure that the Deployer hardcodes its' usage of CF V2 APIs and there's no way to configure it to use V3. This problem hits us trough Spring Cloud Dataflow Server (which internally uses spring-cloud-deployer).
Regards, Daniel Friedman, SAP SAP Metering team.
The move from CF V2 to CF V3 is a major release change, and these are only handled during major release versions of SCDF. This will be SCDF 3.0. We will be announcing the release schedule for SCDF soon.
Description: We are facing an issue with Spring Cloud Data Flow (SCDF) using the Cloud Foundry Deployer. Specifically, it currently hardcodes the usage of the Cloud Foundry (CF) V2 API, which is deprecated in SAP Cloud Foundry. SAP CF has enforced rate limits on the V2 API, which are causing the following error during task deployments:
CF-RateLimitV2APIExceeded(10018): Rate Limit of V2 API Exceeded. Please consider using the V3 API.
Problem: The CF V2 API is deprecated in SAP CF, and its usage is restricted and rate-limited. Unfortunately, Spring Cloud Deployer currently does not provide a configuration option to switch from the V2 API to the V3 API, which makes it impossible for us to avoid these rate limits. This is critically affecting our ability to deploy and manage tasks in SCDF on SAP CF.Request: We would like to request support in the following areas:
Thank you for your attention to this issue. Please let us know if more information is required or if we can assist in any way.
Best Regards, Daniel Friedman, SAP Metering team.