plainbox needs a way to share private scripts within one provider namespace
Bug #1248894 reported by
Zygmunt Krynicki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Critical
|
Zygmunt Krynicki |
Bug Description
With the introduction of multiple providers scripts became a private resource owned by a particular provider. Currently many providers want to "share" their scripts and cross-call them freely. PlainBox needs to setup the PATH of executed scripts so that all providers sharing one namespace are added together.
Related branches
lp:~zyga/checkbox/path-bug
- Sylvain Pineau (community): Approve
-
Diff: 641 lines (+224/-66)2 files modifiedplainbox/plainbox/impl/ctrl.py (+120/-40)
plainbox/plainbox/impl/test_ctrl.py (+104/-26)
Changed in checkbox: | |
status: | In Progress → Fix Committed |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
milestone: | none → plainbox-0.4b1 |
To post a comment you must log in.
So far only resources scripts need to be shared between V1 providers (with two other scripts, filter_template and run_template that could be part of the resource provider btw).
What if plainbox could extend the lookup path with the resource provider path for all providers (v1)?
I don't see other use cases yet and it would give us a working test runner.