set-env no longer accepts empty values
Bug #1388073 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Critical
|
Domas Monkus | ||
Bug Description
A recent change to juju broke set-env, so that it no longer accepts empty values.
In old versions this worked:
juju --show-log set-env -e kvm-upgrade-
In new versions, it gives:
error: expected "key=value", got "tools-
Revision f81cc435 is the first version that our tests show exhibits this bug. We also know that 289da217 did not exhibit this bug.
This is a regression because
- It breaks commandline compatibility with other juju releases
- It breaks CI
| tags: | added: regression |
| Changed in juju-core: | |
| assignee: | nobody → Domas Monkus (tasdomas) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| milestone: | none → 1.21-alpha3 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
