Merge bundled ACLs with custom ones
Metadata
Current evaluation
Enhancement to merge bundled ACLs with custom ones instead of replacing defaults. Triaged but inactive for 299 days.
Suggested action: keep open
Reason: The issue is triaged and represents a legitimate enhancement request from a maintainer (lengau). While inactive for 299 days, there's no evidence it has been addressed or rejected. The referenced issue #491 was closed without a public fix (deferred to Jira FETCH-50), but this ACL-specific enhancement may have different priority or scope.
Impact:
55
Quick Win:
30.25
Staleness:
75
Complexity:
45
Confidence:
65
Support Request:
15
Issue body
### What needs to get done
Implement the same type of fix for https://github.com/canonical/fetch-service/issues/491 but for `acl.yaml`
### Why it needs to get done
If a custom inspectors ACL is given to the fetch service, it is loaded instead of the default configuration shipped with the fetch-service. This behavior forces users (ex. the LP team) to regularly update their custom configuration whenever a new inspector is added, or when the default values change.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
55
Quick Win:
30.25
Staleness:
75
Complexity:
45
Confidence:
65
Support Request:
15
|
keep open | Enhancement to merge bundled ACLs with custom ones instead of replacing defaults. Triaged but inactive for 299 days. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/fetch-service#491
(confidence 85%)
Referenced in the issue body as the similar fix for inspectors configuration that was closed without a public fix (deferred to Jira FETCH-50).
Related issues
No related issues found above the similarity threshold.