New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #9935] Implement support for restoring modified attributes #3285
Comments
Updated by mfriedrich on 2015-08-17 12:53:04 +00:00
|
Updated by mfriedrich on 2015-09-04 12:04:56 +00:00
|
Updated by mfriedrich on 2015-09-04 12:05:08 +00:00
|
Updated by mfriedrich on 2015-09-18 12:51:48 +00:00 There's still something weird going on with modify attribute storing the original_attributes
|
Updated by mfriedrich on 2015-09-18 13:01:32 +00:00 Similar to restoring attributes we should store the real dictionary (vars -> os -> ...) and not the string with indexers inside the original_attributes dictionary. There's one problem with vars - we must always clone the entire vars dictionary and keep it inside the original_attributes dictionary, even if there's one key restored. Restoring the attributes work fine.
|
Updated by mfriedrich on 2015-09-18 13:04:15 +00:00
Applied in changeset 95bcbec. |
Updated by mfriedrich on 2015-09-20 11:18:18 +00:00
We should discuss whether to store the entire indexer and value, or the resolved custom attribute as dictionary. |
Updated by mfriedrich on 2015-09-23 11:30:04 +00:00
Applied in changeset 12cf90c. |
Updated by mfriedrich on 2015-09-24 20:10:32 +00:00
|
Updated by mfriedrich on 2015-11-11 14:48:53 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9935
Created by mfriedrich on 2015-08-17 12:52:43 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-09-23 11:30:03 +00:00)
Target Version: 2.4.0
Last Update: 2015-11-11 14:48:53 +00:00 (in Redmine)
Changesets
2015-09-18 13:01:44 +00:00 by mfriedrich 95bcbec
2015-09-22 13:05:52 +00:00 by mfriedrich da7e78b
2015-09-23 11:29:30 +00:00 by mfriedrich 12cf90c
Parent Task: #9081
The text was updated successfully, but these errors were encountered: