Project

General

Custom queries

Profile

Actions

Bug #7362

closed

Org create dynflow needs to follow the org destroy formula

Added by Partha Aji over 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Orchestration
Target version:
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Org create dynflow currently uses sync actions in the model. This means the dynflow orchestration is called as an after_create. This creates validation issues for bugs relating to create vs update, i.e http://projects.theforeman.org/issues/6946 . Here for example the after_create mode of the org is set to update, which causes the save inside orchestration layer to get confused.

Also in the long term we want a consistent approach for org creation , where the create call actually calls the dynflow action which handles all the orchestration aspects of the org including AR/Candllepin/Pulp/Foreman layers..

Added by Partha Aji over 10 years ago

Revision 896e382f (diff)

Fixes #7362 - Update org create dynflow

Moved it to follow org destroy model. Removed the create orchestration off
sync_action and made the controllers use the orchestrated action
directly. Needed this for tests related to issue #6946 to work.

Also updated unit tests to deal with this change.

Also removed the unused org elastic search bindings

more

more

Added by Partha Aji over 10 years ago

Revision cec576e3

Merge pull request #4642 from parthaa/new-org

Fixes #7362 - Update org create dynflow

Actions

Also available in: Atom PDF