[2.7] actions UX change is not compat with 2.6
Bug #1846792 reported by
Ryan Beisner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Incomplete
|
Low
|
Ian Booth |
Bug Description
The UX surrounding actions CLI has changed in a breaking way from 2.6 to 2.7, causing Charms CI gate tests to break/fail on existing action tests.
If these changes stick, and there is indeed no cli compatibility between the two versions, then libjuju and related functional tests will have to be updated accordingly, which seems like more of a major-version change experience.
Changed in juju: | |
status: | New → Incomplete |
Changed in juju: | |
status: | Incomplete → New |
Changed in juju: | |
milestone: | none → 2.7-beta1 |
assignee: | nobody → Ian Booth (wallyworld) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.7-rc1 |
Changed in juju: | |
milestone: | 2.7-rc1 → none |
To post a comment you must log in.
Any incompatibility is unintentional.
We are using a feature flag "juju-v3" to hide the new actions UX. There is one change that is exposed to 2.6 which is that action ids are now numbers instead of UUIDs. But action ids are supposed to be opaque anyway and callers should not depend on them being any particular format. Is the change in action id the problem you are referring to or is there something else?