Environment variable not expanded in packages entries
Bug #2002411 reported by
jeremie
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lpci |
Triaged
|
Low
|
Unassigned |
Bug Description
Environment variables aren't expanded when used in packages entries, e.g. the following fails,
```
pipeline:
- test
jobs:
test:
series: focal
run: echo hello world >output
packages: [$mypackage]
```
Note that adding quotes/ticks doesn't help.
Changed in lpcraft: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
We had no intention to do that, at least not in the beginning, so I regard this a feature request.
Similar to YAML aliases and YAML includes, I would like to direct the discussion to https:/ /chat.canonical .com/canonical/ pl/r71cgk3ejtr1 zmbfnfitbi187c where I suggested to use an external client side tool / script / one-liner to do all expansion, so there would be no changes necessary to the CI runner.