Create a way to adjust the operator endpoint when not using the charm plugin
Metadata
Current evaluation
Auto-generated dispatch files outside the charm plugin still default to src/charm.py; the entrypoint override remains a TODO, leaving non-default operator entrypoints unsupported.
Suggested action: keep open
Reason: LifecycleService.post_prime still contains “TODO: include an entrypoint override. #1896” and calls create_dispatch() without its existing entrypoint parameter. This is a valid, tightly scoped parity gap, and the helper already supports custom entrypoints, so implementation can proceed without further clarification.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
43
Quick Win:
22
Complexity:
38
Confidence:
96
Actionability:
84
|
keep open | Auto-generated dispatch files outside the charm plugin still default to src/charm.py; the entrypoint override remains a TODO, leaving non-default operator entrypoints unsupported. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
17
Complexity:
30
Confidence:
70
Actionability:
60
|
needs triage | Feature request to allow configuring the operator entrypoint in non-charm plugins (poetry, python, uv) for dispatch file parity with the charm plugin. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21
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. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#1898
(confidence 96%)
That change added dispatch auto-generation when none exists, but left the entrypoint override as the current TODO.
Related issues
No related issues found above the similarity threshold.