The change altered the model_template notebook and added 2 sections and will be visible in the "model.Name" notebook.
The logic will execute a notebook with the ".preexecute" suffix before the SQL code and a notebook with the ".postexecute" suffix after the SQL code executed. These notebooks are not created by the framework and allows customers the flexability for custom notebooks to execute before and after the framework generated code.
Notebook name created by the framework "model.issue42.my_first_dbt_model"
Notebook name to executed before: "model.issue42.my_first_dbt_model.preexecute"
Notebook name to executed before: "model.issue42.my_first_dbt_model.postexecute"
If the notebook does not exist a message will be shown as seen in image 1
A sample of a notebook postexecute can be seen in image 2
To confirm if the logic works create a notebook with the preexecute and postexecute suffix and add this code to it:
Issue #42
The change altered the model_template notebook and added 2 sections and will be visible in the "model.Name" notebook.
The logic will execute a notebook with the ".preexecute" suffix before the SQL code and a notebook with the ".postexecute" suffix after the SQL code executed. These notebooks are not created by the framework and allows customers the flexability for custom notebooks to execute before and after the framework generated code.
Notebook name created by the framework "model.issue42.my_first_dbt_model" Notebook name to executed before: "model.issue42.my_first_dbt_model.preexecute" Notebook name to executed before: "model.issue42.my_first_dbt_model.postexecute"
If the notebook does not exist a message will be shown as seen in image 1 A sample of a notebook postexecute can be seen in image 2
To confirm if the logic works create a notebook with the preexecute and postexecute suffix and add this code to it:
df = 'Testing Issue42 Custom Notebook Execution' display(df)