Create a way to adjust the operator endpoint when not using the charm plugin
Metadata
Current evaluation
Feature request to allow configuring the operator entrypoint when auto-generating the dispatch file without the charm plugin, for feature parity. A TODO in lifecycle.py still references #1896, confirming it is unimplemented. No labels, no maintainer triage, last activity ~12.5 months ago.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and no maintainer response beyond the Jira-sync bot comment. Although a TODO in charmcraft/services/lifecycle.py (line 71) explicitly references #1896 and the author is a maintainer, the issue itself has not been categorised, prioritised, or assigned in the tracker. It should be triaged to determine whether it will be scheduled or closed as out-of-scope.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21.0
Staleness:
60
Complexity:
40
Confidence:
78
Support Request:
10
|
needs triage | Feature request to allow configuring the operator entrypoint when auto-generating the dispatch file without the charm plugin, for feature parity. A TODO in lifecycle.py still references #1896, confirming it is unimplemented. No labels, no maintainer triage, last activity ~12.5 months ago. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
35
Confidence:
85
Support Request:
10
|
close stale | Request to configure the operator endpoint during non-charm dispatch file generation for feature parity. Currently unlabelled and inactive for over a year with no maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
20
Confidence:
70
Support Request:
10
|
needs triage | Feature request to allow configuring the operator entrypoint in auto-generated dispatch files without the charm plugin for feature parity. Currently unlabelled and inactive for over a year with only an automated Jira ticket response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
65
Support Request:
10
|
needs triage | Feature request to allow customizing the operator endpoint in auto-generated dispatch files without the charm plugin. Currently unlabelled, unassigned, and inactive for over a year with only an automated Jira sync comment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
30
Confidence:
75
Support Request:
0
|
needs triage | Enable custom operator entrypoint configuration in auto-generated dispatch files without the charm plugin for feature parity. Open, linked to internal Jira ticket CRAFT-3377. Awaiting implementation or assignment after 304 days of inactivity. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#1898
(confidence 90%)
PR #1898 introduced the auto-generation of the dispatch file (the feature this issue extends). The TODO in lifecycle.py was added as part of that work.
Related issues
No related issues found above the similarity threshold.