Remove repository lock from V3 Collection Import endpoint #1115
Conversation
| with repository.new_version() as new_version: | ||
| new_version.add_content(content_q) | ||
| CreatedResource.objects.create(content_object=repository) | ||
| if not lockless: |
There was a problem hiding this comment.
You could try to see if the repository was in the locks of this task and decide that way.
WDYT?
|
@gerrod3 I think we need to make some additional changes to the collection import changes anyway. There are some fields that are missing which are in the galaxy_ng implementation |
I see the galaxy collection import has a reference to the namespace model. So this work needs to wait till the namespace model has been moved. |
|
This pull request has been marked 'stale' due to lack of recent activity. If there is no further activity, the PR will be closed in another 30 days. Thank you for your contribution! |
|
This pull request has been closed due to inactivity. If you feel this is in error, please reopen the pull request or file a new PR with the relevant details. |
fixes: #1105
Right now this is the bare minimum changes required to remove the repository lock from the initial import task. However, I think we should look into changing the
CollectionImportmodel to accommodate for the new task group which would require a migration. @newswangerdTODO:
CollectionImportmodel should report