Added cloud sql restore module that uses database import #343
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
|
@ravi-dalal |
bharathkkb
approved these changes
Oct 7, 2022
| 4. Fetch the SQL export file(s) from GCS and import those into the import database instance | ||
| 5. The import API call is asynchronous, so the workflow checks the status of the import at regular interval and wait until it finishes | ||
|
|
||
| ## How to run |
There was a problem hiding this comment.
Might be useful in a follow up to add some CUJs around when to use this vs gcloud.
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.
The restore module is using Cloud SQL Import API call through a Workflow. This module is an extension of backup module's export function.