service route binding: migrate to ccv3 #10
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
Cocossoul
changed the title
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.
Does this PR modify CLI v6 or v7?
No
Description of the Change
This PR adds the new ccv3 resource : service route binding. It is basically a copy and paste of the code of the official provider.
Why Is This PR Valuable?
It allows migrating the service route binding resource in the Terraform provider to v3. SAP BTP does not support v2 API anymore, so for the Terraform provider to work we need to migrate its resources to v3.
PR in Terraform provider: cloudfoundry-community/terraform-provider-cloudfoundry#572
How urgent is the change?
Since we cannot use the v2 resources API in SAP BTP, we currently cannot manage service route bindings the Terraform provider, which makes it kind of urgent.