Tags: Roche/foxops
Tags
unify the logic how the provided template data is stored (#456) unify the logic how the provided template data is stored to prevent inconsistencies between creation/updates of an incarnation, the .fengine.yaml template_data is now configured to always contain all the data provided by the user. No longer limiting it to values that are provided for valid variables or that are different from the defaults
add support for complex variables (lists, nested objects) (#427) * * fully remove the no longer functioning "allow_import" variable on the create incarnation endpoint * remove support for fvars file * add support for complex template variables (lists, nested objects) * proper handling of template variables with defaults in incarnations (default values will not be fixed anymore - if a default is not specified explictly when creating an incarnation, it will be changed on an incarnation update, if the default changed in the template) * fixed handling of legacy incarnations and default values for nested variables * fixed incorrect responses from the API * avoid storing additionally provided template variables in the incarnation state ... if they are not defined in the template interface * updated docs and fixed a small bug
PreviousNext