Some configurations are not only applicable for the generation of api-schema, resolvers and which driver to select etc.. Some are also relevant when actually running the driver (as they are setup now).
Currently field_for_creation_date and field_for_last_update_date are both expected to always be set to true in the driver, and actually setting them to false would lead to errors when creating objects etc., as the driver would try to insert fields that does not exists.

How to solve this might not be obvious. My suggestions would be to either keep keep the relevant configurations as actually values in the drivers file(s), or have lines in the driver(s) files that are added/removed dynamically during generations depending on the configurations.

I should have realized this earlier....

@hartig @keski @rcapshaw