Allow Custom Error Categorization rules to be defined in templates or as a shared resource
M
Mint Locust
Custom Error Categorization rules can only come from a file in the stage workspace (HARNESS_ERRORS_YAML_PATH or .harness/errors.yaml). You can't define them inline.
That makes it hard for teams that support many pipelines through shared templates. Today the options are:
- Commit errors.yaml to every repository. The copies drift apart, and every change needs a PR in every repo.
- Add a step to fetch a shared file in every stage. Each run gets slower and there's more custom setup to maintain.
Proposed solution (either would help):
- Inline rules: Let rules be declared in pipeline, stage, and step group YAML, including templates. Pipelines that use a template would inherit its rules.
- Shared rule sets: Let rule sets be created at the account, org, or project level and referenced from pipelines and templates.