tal-device-configs

TAL Device Configs

These are the private (BBC Internal) device configs for TAL - which eventually feed into the public versions:

• https://github.com/fmtvp/tal/tree/master/config/devices

Where are they used?

TAL Device Configs are used:

• by TAP Launcher, merged with the TAP Device Configs, and then served up to specific devices based on brand and model
• by CATAL Launcher, merged with the CATAL Device Configs, and then served up to specific devices based on brand and model

Public npm module

When this project is published via

npm publish

The module that is published contains ONLY example-example-default.json and example-example-precert.json configs (plus other required files) as a sanitised version usable by Partners and external stakeholders.

Releasing

Changes to this project are automatically deployed to S3, and then promoted to the INT environment, available through:

• https://www.live.bbctvapps.co.uk/catal
• https://www.live.bbctvapps.co.uk/tap/iplayer

TAL Device Configs are released in the same build job as CATAL Device Configs. The actual configs are not copied anywhere during this step; instead, a pointer file containing the commit hash is updated, instructing the Launcher for a specific environment to switch over to the new configs.

The build jobs to use:

• deploy-tal-device-configs (builds automatically on push)
• promote-catal-device-configs-to-test
• promote-catal-device-configs-to-live

Access to these jobs is restricted to members of the Connected TV Development team; your email address will need to be added to the Connected TV Cloud Jenkins whitelist to access these jobs.