1 error mapping for multiple services
Use case: A team has 15 services that log similar errors, instead of ‘teaching’ Harness 15 times, we can have a ‘shared’ mapping used by all deployments
Pre-register errors upfront - before they are flagged during the deployment
Use case:
Partially solves above issue
Also covers use case when we introduce new Flogs that we know might get thrown during deployments