Add env configuration to baseplugin
Metadata
Current evaluation
Request to add env configuration to base plugin so environment variables can be set in yaml. Feature is already available via the part-level build-environment key in craft-parts, making this obsolete.
Suggested action: close stale
Reason: The issue is ~10 years old with zero comments or maintainer interaction. The requested capability (setting environment variables in yaml) is already implemented as the part-level build-environment property in craft-parts, documented in part_properties.rst and used extensively across plugin docs and tests.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
12.0
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | Request to add env configuration to base plugin so environment variables can be set in yaml. Feature is already available via the part-level build-environment key in craft-parts, making this obsolete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Request to extend baseplugin schema to accept environment variables in YAML, avoiding per-plugin setup. Untriaged, inactive for nearly a decade, with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request to expose environment variable configuration via YAML in the base plugin. The issue has been inactive for nearly 10 years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Feature request to add YAML-based environment variable configuration to the base plugin, leveraging an existing env() method. Untriaged, inactive for over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Proposes extending the base plugin schema to configure environment variables via YAML, utilizing the existing env() method. Open, unassigned, inactive, and awaiting triage with no comments. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-parts#1608
(confidence 60%)
feat: allow applications to set build environment — the build-environment part property provides the requested yaml-based env configuration
Related issues
No related issues found above the similarity threshold.