Skip to content
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

Combine the copy and remove tasks #1122

Merged
merged 1 commit into from
Feb 10, 2022

Conversation

awcrosby
Copy link
Contributor

@awcrosby awcrosby commented Feb 9, 2022

Description 🛠

For copying and removing content from a repository, currently 2 tasks
are called. Changing to be 1 task so lock and transaction can occur in
a single task. Pulls work done by @rochacbruno from #1076.

Issue: AAH-1349

Reviewer Checklists 👀

Developer reviewer:

  • Code looks sound, good architectural decisions, no code smells
  • There is a Jira issue associated (note that "No-Issue" should be rarely used)
  • Tests are included in galaxy_ng/tests/integration or galaxy_ng/tests/functional, and they fully cover necessary test scenarios… or tests not needed

QE reviewer (exceptions):

  • Tests are included in galaxy_ng/tests/integration or galaxy_ng/tests/functional, and they fully cover necessary test scenarios… or tests not needed
  • PR meets applicable Acceptance Criteria for associated Jira issue

Note: when merging, include the Jira issue link in the squashed commit

@awcrosby awcrosby force-pushed the fix/combine_tasks_copy_remove branch from 9b180b2 to 90cfdb4 Compare February 9, 2022 16:29
@awcrosby awcrosby marked this pull request as ready for review February 9, 2022 17:41
@awcrosby
Copy link
Contributor Author

awcrosby commented Feb 9, 2022

@rochacbruno I still have a unit test I want to update but this is ready for review. I am hoping you can include the signature pieces in the move_content() content obj without the need for _remove_content_from_repository.

@awcrosby awcrosby added backport-4.3 This PR should be backported to stable-4.3 (2.0) backport-4.4 This PR should be backported to stable-4.4 (2.1) labels Feb 9, 2022
Ensure copy and remove tasks are run in sequence by combining from 2
tasks into 1, where they share the same locks. Avoids scenario where 1
task can fail and the other can succeed.

Issue: AAH-1349
@awcrosby awcrosby force-pushed the fix/combine_tasks_copy_remove branch from 8f98032 to 5c41f4c Compare February 10, 2022 14:26
@awcrosby awcrosby merged commit 0608454 into ansible:master Feb 10, 2022
@awcrosby awcrosby deleted the fix/combine_tasks_copy_remove branch February 10, 2022 15:52
@ansible ansible deleted a comment from patchback bot Feb 11, 2022
@ansible ansible deleted a comment from patchback bot Feb 11, 2022
awcrosby added a commit to awcrosby/galaxy_ng that referenced this pull request Feb 11, 2022
Ensure copy and remove tasks are run in sequence by combining from 2
tasks into 1, where they share the same locks. Avoids scenario where 1
task can fail and the other can succeed.

Issue: AAH-1349
(cherry picked from commit 0608454)
awcrosby added a commit to awcrosby/galaxy_ng that referenced this pull request Mar 15, 2022
Ensure copy and remove tasks are run in sequence by combining from 2
tasks into 1, where they share the same locks. Avoids scenario where 1
task can fail and the other can succeed.

Issue: AAH-1349
(cherry picked from commit 0608454)
awcrosby added a commit that referenced this pull request Mar 17, 2022
Ensure copy and remove tasks are run in sequence by combining from 2
tasks into 1, where they share the same locks. Avoids scenario where 1
task can fail and the other can succeed.

Issue: AAH-1349
(cherry picked from commit 0608454)
@github-actions github-actions bot added the backported-4.4 This PR has been backported to stable-4.4 (2.1) label Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-4.3 This PR should be backported to stable-4.3 (2.0) backport-4.4 This PR should be backported to stable-4.4 (2.1) backported-4.4 This PR has been backported to stable-4.4 (2.1)
Projects
None yet
2 participants