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 Support in Migrating to CF V3 API in Spring Cloud Deployer Due to SAP CF Deprecation of V2 API #479

Open
DanFrei opened this issue Sep 24, 2024 · 3 comments
Labels
status/need-feedback Calling participant to provide feedback

Comments

@DanFrei
Copy link

DanFrei commented Sep 24, 2024

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:

  1. Migration to V3 API: Can you please provide a timeline or plan for when Spring Cloud Deployer will support the CF V3 API?
  2. Temporary Workaround: In the meantime, is there any possible workaround or patch that could help us mitigate this issue until the V3 API is supported?

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.

@corneil
Copy link
Contributor

corneil commented Sep 27, 2024

@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.

@cppwfs cppwfs added status/need-feedback Calling participant to provide feedback and removed status/need-triage Team needs to triage and take a first look labels Sep 30, 2024
@DanFrei
Copy link
Author

DanFrei commented Oct 1, 2024

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.

@github-actions github-actions bot added for/team-attention For team attention and removed status/need-feedback Calling participant to provide feedback labels Oct 1, 2024
@cppwfs
Copy link
Contributor

cppwfs commented Oct 1, 2024

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.

@github-actions github-actions bot added status/need-feedback Calling participant to provide feedback and removed for/team-attention For team attention labels Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/need-feedback Calling participant to provide feedback
Projects
None yet
Development

No branches or pull requests

3 participants