Read playlist information from Steering API, instead of Tank API

Parent: [EPIC] Refactor playlist and metadata management (aura#155 - closed)

As part of the parent epic, Tank Playlist information is pushed to Steering upon assignment to a Timeslot. Additional Playlist Metainformation might be added to Steering timeslots also.

This means all playlist data can be read together with other calendar information using a single GET request to /steering/api/v1/playout.

As a consequence this also has some positive non-functional effects:

• Reduced API requests per scheduling cycle (currently 1 to Steering and (n) to Tank for every single playlist, every 30 seconds)
• De-coupling of Engine and Tank. The only API interaction left between these two, is on a file-system basis when accessing audio files.

changed milestone to %1.0-alpha2 — Precise Pheasant

added P2 label

assigned to @david

marked this issue as related to aura#96 (closed)

marked this issue as related to steering#130

marked this issue as related to dashboard#114 (closed)

marked this issue as related to tank#38 (closed)

marked this issue as related to steering#107 (closed)

mentioned in issue aura#96 (closed)

Initially Playlistinfo can be read via the planned Steering API proxy (See API endpoint to provide playlist information (steering#136 - closed)). At a later stage we can also use #Extend Playout API Endpoint to include all play... (steering#130)

changed milestone to %1.0-alpha5 — Capable Capybara

changed milestone to %1.1

removed the relation with aura#96 (closed)

removed the relation with tank#38 (closed)

unassigned @david

changed milestone to %1.0-alpha6 — Wondrous Whale

changed the description

added requires-refinement label

assigned to @chrizz

mentioned in issue aura#155 (closed)