← Back to issue list

add ability to add / update run_managed env

View original Github issue

Metadata

Project
craft-application
Number
#572
Type
issue
State
open
Author
dariuszd21
Labels
Created
Updated
Closed

Current evaluation

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.

Suggested action: needs triage

Reason: The issue is a well-scoped feature request from a maintainer (dariuszd21) with a concrete code reference, but it has no labels, no assignee, and the only comment is the automated Jira sync bot (CRAFT-3740) — no human triage or acknowledgement. The hardcoded env dict still exists in ProviderService.run_managed (craft_application/services/provider.py:564-567), so the request remains valid and unimplemented. It should be triaged and categorised before any close decision.

Impact: 45 Quick Win: 27.0 Staleness: 70 Complexity: 40 Confidence: 75 Support Request: 10

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
qwen/qwen3.8-27b
Impact: 45
Quick Win: 27.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 20
Confidence: 75
Support Request: 10
needs triage Add _extra_managed_env() method to allow apps to dynamically set environment variables for managed runs, replacing hardcoded values. Open, inactive for over a year, synced to Jira CRAFT-3740. Awaiting triage and assignment.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.