RSE-734 Fix: Asynchronous Project Import #535
Merged
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
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.
RSE-734 Fix: Asynchronous Project Import
To start new asynchronous import process and request status of an ongoing process.
To QA 🧪
To call the new importer, make sure you have the right environment variables, but the most important of all is this:
RD_HTTP_TIMEOUT = 21600because if we update a big file, the first phase of the import is transactional, a timeout could end in a rollback.Then, call the endpoint with something like this:
rd-cli.jar -jar projects archives import -cairs -f /path/to/file/project.jar --project=my-project(the "i" hyphen trigger the async import)Once the api returns the "started" message, request status:
rd-cli.jar -jar projects archives async-import-status --project=my-project