add ability to add / update run_managed env
Metadata
Current evaluation
Feature request to add an `_extra_managed_env()` hook so applications can inject/update environment variables for managed runs; currently unimplemented and unlabelled.
Suggested action: keep open
Reason: Maintainer-filed feature request with a clear goal, and an internal Jira ticket (CRAFT-3740) was created, indicating it was triaged. Repository search shows no `_extra_managed_env` implementation, and `ProviderService.run_managed` still hardcodes the managed environment, so the issue remains valid and open.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
12
Complexity:
55
Confidence:
70
Actionability:
60
Issue body
### What needs to get done
Add `_extra_managed_env()` method to the application that will be used to update the mentioned dict before command is run
### Why it needs to get done
Current implementation have a hardcoded set of environmental variables to be passed to managed run. We need an ability to pass it on the application basis
https://github.com/canonical/craft-application/blob/50cb666f911a139044d046179b53eb49bbd7644d/craft_application/application.py#L425-L428
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
45
Quick Win:
12
Complexity:
55
Confidence:
70
Actionability:
60
|
keep open | Feature request to add an `_extra_managed_env()` hook so applications can inject/update environment variables for managed runs; currently unimplemented and unlabelled. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
15
Complexity:
25
Confidence:
58
Actionability:
70
|
needs triage | Maintainer-filed feature request to add a `_extra_managed_env()` hook on Application so subclasses can inject/update env vars for managed runs; unlabelled, only an automated Jira-sync bot comment, still unimplemented. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
23
Complexity:
25
Confidence:
88
Actionability:
76
|
needs triage | Requests an application-level `_extra_managed_env()` hook to extend or override environment variables before managed commands run; it remains open and untriaged. | |
| qwen/qwen3.6-35b-a3b |
Impact:
40
Quick Win:
22
Complexity:
30
Confidence:
70
Actionability:
80
|
needs triage | Feature request to add _extra_managed_env() method for custom environment variables in managed runs. Unlabelled, no maintainer response in 660 days. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
27
Staleness:
70
Complexity:
40
Confidence:
75
Support Request:
10
|
needs triage | Feature request to add an _extra_managed_env() hook on Application so apps can extend the environment variables passed to managed runs, which are currently hardcoded in ProviderService.run_managed. Open since Nov 2024 with no maintainer response beyond the Jira sync bot; no labels or assignee. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
35
Confidence:
80
Support Request:
10
|
needs triage | Feature request to add a customizable extra_managed_env method for passing application-specific environment variables to managed runs instead of hardcoded values. Currently inactive for over a year with no maintainer triage or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
80
Support Request:
10
|
needs triage | Feature request to allow custom environment variables in managed runs via a new method. Untriaged, lacks labels or maintainer response, and has been inactive for over 18 months. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.