Hi @mkolonay,

I can suggest two approaches:

1. Store widget values outside the notebook in a separate configuration file. When a notebook is executed, a script can dynamically read the configuration file and set the widget values accordingly. This approach ensures that the widget values are not embedded within the notebook file itself and therefore remain out of source control

2. Utilize dbutils.widgets and their fallback values:

* Local Implementation: Implement a mechanism to set default values from a local script or environment variables.
* Interactive Widgets: If the interactive environment (like Jupyter) does not set the widget values, the widgets should fall back to default values specified in the local script