Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for V3 API Support in Spring Cloud Data Flow Server to Avoid CF-RateLimitV2APIExceeded Error #5951

Closed
DanFrei opened this issue Sep 23, 2024 · 2 comments

Comments

@DanFrei
Copy link

DanFrei commented Sep 23, 2024

Description:
We at SAP, are encountering the following error while deploying tasks using Spring Cloud Data Flow Server:
CF-RateLimitV2APIExceeded(10018): Rate Limit of V2 API Exceeded. Please consider using the V3 API.

This error occurs because SAP Cloud Foundry has deprecated the V2 API, and its usage is now rate-limited as part of the SAP CF API v2 Deprecation and Removal Plan. However, Spring Cloud Data Flow Server still relies on the V2 API via the Spring Deployer, which appears to be hardcoded, and there is no way to configure the server to use the V3 API
The deprecation of the V2 API and subsequent rate-limiting severely impacts task deployments, causing delays and failures in our pipeline.

Could you please provide a fix that would make it configurable?

Release versions:
Name: spring-cloud-dataflow-server
Version: 2.11.3
Commit: 2183849

Screenshots:
Screenshot 2024-09-23 at 18 18 12

@cppwfs
Copy link
Contributor

cppwfs commented Sep 24, 2024

Related to: spring-cloud/spring-cloud-deployer#479

@cppwfs
Copy link
Contributor

cppwfs commented Sep 30, 2024

Closing this as a duplicate of : spring-cloud/spring-cloud-deployer#479

@cppwfs cppwfs closed this as completed Sep 30, 2024
@cppwfs cppwfs removed the status/need-triage Team needs to triage and take a first look label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants