Switching to CloudFoundry v3 API #148
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Kump3r <[email protected]>
|
These two docs are helpful for reviewing: |
taylorsilva
reviewed
Oct 15, 2024
There was a problem hiding this comment.
One a first red through it looks like this migration is easy: https://v3-apidocs.cloudfoundry.org/version/3.179.0/index.html#users-and-roles-in-v3
I'll dive deeper into this once 7.12.0 is out the door. Thanks again for the PR!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Switch to CF API v3, because of [RFC] CF API v2 End of Life
What this PR does / why we need it
Concourse issue #9006
Special notes for your reviewer
N/A
Does this PR introduce a user-facing change?
No, backwards compatible