Actions
Architecture #3230
closed
Transactionnal behavior accros several, non-transactionnal backend
Status:
Released
Priority:
1 (highest)
Assignee:
-
Category:
Architecture - Code maintenance
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
We need to buld a (false) transactionnal behavior accross our différent non-transactionnal back-end (LDAP, FS, other DB) to allows to garanty some consistency at the application level.
See http://www.rudder-project.org/redmine/issues/3211 for details.
Updated by François ARMAND almost 12 years ago
Some code is live in FAR repositories, see (for example): https://github.com/fanf/rudder/tree/bug_3211/dev/transactionnal_behavior_on_config
Updated by Nicolas PERRON over 11 years ago
- Status changed from 12 to Pending release
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Pending release to Released
This ticket has been addressed in version 2.6.0~beta1 of Rudder, which has just been released. Please see the changelog here: https://www.rudder-project.org/foswiki/System/Documentation:ChangeLog26.
Actions