Actions
Refactor #9012
closedThe manifest actions in dynflow ought to rely on other actions for deleting repos and products, etc
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
-
Description
I noticed that the actions we have in dynflow for refreshing, deleting, etc manifests are very basic and rely on code mostly in the glue layer. This glue layer code does things like deleting products, repos, etc. A better design would be to use dynflow actions to perform these things.
Actions