generated from SAP/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 3
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
[FEATURE] Migration Document #70
Labels
Comments
lechnerc77
added
enhancement
New feature or request
pending-decision
This issue has not been accepted for implementation nor rejected. It's still open to discussion.
labels
Apr 4, 2024
Thanks for the feature request. We evaluate it and update the issue accordingly. Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This makes sense and adds value. We will start working on this parallely. |
vipinvkmenon
removed
the
pending-decision
This issue has not been accepted for implementation nor rejected. It's still open to discussion.
label
Apr 4, 2024
Planned for next week. |
Love this! If at all possible, I'd like for this repository to be approached with migration in mind:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What area do you want to see improved?
documentation
Is your feature request related to a problem? Please describe.
When releasing the new provider we must guide user already using the Cloud Foundry Comunity provider on their way to switching over to the new provider.
The parameterization a s well as parameters names might deviate and also resources might be different, so we should make the transition as easy as possible.
Describe the solution you would like
I could think of a document (Markdown in this repository referenced from the documentation on the Terraform registry) that compares the setup of the same resource in a "before/after" kind of setup.
Example (not nice, but explains the idea:
Describe alternatives you have considered
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: