You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exporting Custom Datafields using Configuration Baskets should also export Datafield Categories.
Current Behavior
Exporting Custom Datafields with Configuration Baskets ignores Datafield Categories. Definitions of datafield categories as well as assignment of datafields to categories get lost during export.
Possible Solution
Steps to Reproduce (for bugs)
add a new datafield category
create a new datafield
assign newly created category to newly created datafield
create one config basket exporting everything
import configuration basket into a new director installation
=> the newly created datafield gets imported - the datafield category is missing (the assignment of the datafield to the category either, i.e. the ID in the database in column category_id = NULL)
Your Environment
Director version (System - About): 1.8.0
Icinga Web 2 version and modules (System - About): 2.8.2
With 1.8.1 and the current master the behavior has changed in the way it complains about an "Integrity constraint violation" during restore of the snapshot as in the basket the id of the category is stored for the field, but the category is not (as far as I can see it), so it is worse than before in my eyes.
Expected Behavior
Exporting Custom Datafields using Configuration Baskets should also export Datafield Categories.
Current Behavior
Exporting Custom Datafields with Configuration Baskets ignores Datafield Categories. Definitions of datafield categories as well as assignment of datafields to categories get lost during export.
Possible Solution
Steps to Reproduce (for bugs)
=> the newly created datafield gets imported - the datafield category is missing (the assignment of the datafield to the category either, i.e. the ID in the database in column category_id = NULL)
Your Environment
icinga2 --version
): r2.12.1-1The text was updated successfully, but these errors were encountered: