plainbox session export should have an option to ignore job compatibility checks
Bug #1378296 reported by
Zygmunt Krynicki
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| PlainBox (Toolkit) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Currently any change to any job definition that participated in a session renders such a session impossible to resume.
For handling exports though (generating reports from a session) it should still be possible to override that check with a command line switch. This would allow us to resume past sessions as long as a job with the same ID still exists, even if we had changed that job somehow.
| Changed in plainbox: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Zygmunt Krynicki (zkrynicki) |
| Changed in plainbox: | |
| assignee: | Zygmunt Krynicki (zyga) → nobody |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in plainbox: | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Well, this is actually implemented.
$ plainbox session export --flag ignore-