Skip to content

Conversation

@kathap
Copy link
Contributor

@kathap kathap commented Mar 27, 2025

  • A short explanation of the proposed change:
    /v2/info was currently excluded from v2 rate limiting. Don't rate limit and keep /v2/info even when CF API v2 is switched off.

  • An explanation of the use cases your change solves
    /v2/info endpoint is still available when cc.temporary_enable_v2=false and indicates that v2 is disabled.

  • Links to any other associated PRs

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

@kathap kathap marked this pull request as draft March 27, 2025 15:51
@kathap kathap force-pushed the keep-v2-info-endpoint-when-v2-is-disabled branch from bcac140 to bdb4d73 Compare March 27, 2025 16:00
@kathap kathap marked this pull request as ready for review March 28, 2025 09:45
@kathap kathap merged commit 04c46ec into main Apr 7, 2025
8 checks passed
ari-wg-gitbot added a commit to cloudfoundry/capi-release that referenced this pull request Apr 7, 2025
Changes in cloud_controller_ng:

- Keep /v2/info endpoint when v2 is disabled
    PR: cloudfoundry/cloud_controller_ng#4280
    Author: Katharina Przybill <[email protected]>
@moleske moleske deleted the keep-v2-info-endpoint-when-v2-is-disabled branch April 7, 2025 15:17
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

Successfully merging this pull request may close these issues.

2 participants