Details
-
Task
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
Description
Expose some of the tasks in mgnl management app to https://console.foundation.magnolia-cloud.com/ so we can run them easily in case something goes awry
See https://magnolia-cms.slack.com/archives/C02REMXERJ8/p1674812127268109
- the bulk of the work would be to split them all away into independent commands
- e.g. one task SLACK_ANNOUNCE with different params (msg, target channel)
how to manage the Nexus observation?as of today there is one cron-like job that observes nexus and triggers a somewhat ordered list of taskswe should have a list of tasks that themselves observe nexususing an abstract class that would share the Nexus monitoring logic
Or maybe one task that observes nexus and triggers the child tasks when it deems necessary?in order to manage the order of the list, use AWS Simple Workflow Service where necessaryfirst, the child tasks (unordered), then announcing the release in #pd
- optional: look into a dry-run mode? As the tasks aren't run often but have a big impact, we should implement them so that they do no harm
Checklists
Acceptance criteria