[BUILD-1005] Expose more tasks to console foundation app Created: 27/Jan/23  Updated: 27/Nov/23  Resolved: 27/Nov/23

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Team: Foundation
Work Started:

 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 tasks
    • we should have a list of tasks that themselves observe nexus
      • using 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 necessary
      • first, 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

 



 Comments   
Comment by Maxime Michel [ 27/Nov/23 ]

Looks obsolete to me, feel free to reopen if you disagree.

Generated at Sun Feb 11 23:47:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.