Project

General

Profile

Bug #9416

Content View update - needs to be dynflow'ed

Added by Brad Buckingham about 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Brad Buckingham
Category:
Content Views
Target version:
Katello 2.2
Difficulty:
Triaged:
Yes
Bugzilla link:
1194784
Pull request:
https://github.com/Katello/katello/pull/5018
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

In certain scenarios, performing a content view update will initiate a reindex of association objects (e.g. repositories) during an update. As a result, this action should be dynflow'ed as has been done for similar update actions on other objects.

Associated revisions

Revision 7666b964 (diff)
Added by Brad Buckingham about 8 years ago

fixes #9416 - content view update - dynflow'ize it

Converted the content view update action to use dynflow. Since
this action uses elasticsearch to update relationships, it should
be using dynflow.

This becomes more important for plugins like fusor, which will
create custom actions involving content view updating.

Revision 940cc7f9
Added by Brad Buckingham about 8 years ago

Merge pull request #5018 from bbuckingham/issue-9416

fixes #9416 - content view update - dynflow'ize it

History

#1 Updated by Brad Buckingham about 8 years ago

  • Category set to Content Views

#2 Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 66
  • Pull request https://github.com/Katello/katello/pull/5018 added
  • Pull request deleted ()

#3 Updated by Brad Buckingham about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Brad Buckingham about 8 years ago

  • Bugzilla link set to 1194784

#5 Updated by Eric Helms about 8 years ago

  • Legacy Backlogs Release (now unused) set to 23

Also available in: Atom PDF