Hook execution context/cache is needed
Bug #676286 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Medium
|
Kapil Thangavelu | ||
Bug Description
As per the mailing list discussion, values retrieved by hooks are cached, and the cache itself tracks if a dirty read has been issued ( a read prior to a subsequent change), so that the hook can be rescheduled for execution. This cache is the basis of an execution object that is associated to the hook cli api for the duration of hook execution.
Related branches
lp:~hazmat/pyjuju/hook-execution-state
- Gustavo Niemeyer: Approve
-
Diff: 1030 lines (+803/-97)9 files modifiedensemble/hooks/__init__.py (+1/-0)
ensemble/hooks/tests/__init__.py (+1/-0)
ensemble/lib/testing.py (+9/-0)
ensemble/state/hook.py (+257/-0)
ensemble/state/relation.py (+46/-18)
ensemble/state/tests/test_hook.py (+322/-0)
ensemble/state/tests/test_relation.py (+115/-79)
ensemble/state/tests/test_topology.py (+36/-0)
ensemble/state/topology.py (+16/-0)
| Changed in ensemble: | |
| assignee: | nobody → Kapil Thangavelu (hazmat) |
| status: | New → In Progress |
| milestone: | none → 0.3 |
| Changed in ensemble: | |
| importance: | Undecided → Medium |
| Changed in ensemble: | |
| status: | In Progress → Fix Committed |
| Changed in ensemble: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
