The manifest actions in dynflow ought to rely on other actions for deleting repos and products, etc
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.
#3 Updated by John Mitsch about 2 months ago
- Target version deleted (
- Status changed from New to Rejected
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.