Which two configurations can customize Transform Logic Level Versioning (TLLV) in Foundry?

Customizing Transform Logic Level Versioning (TLLV) in Foundry involves configuring how versioning tracks changes and dependencies within your data transformations. The selected answer highlights one of the key methods of doing this.

Adding tllvFiles with specific file paths in the transformsPython configuration allows you to explicitly define which files should be included in TLLV tracking. By doing this, you can better manage how changes in specific scripts or files impact the versioning of transformations. This targeted approach provides fine-grained control, ensuring that only designated transformations are affected by versioning constraints, thus facilitating precise management of data dependencies and their relationships.

This level of specificity helps in scenarios where transformations may depend on multiple scripts or files, allowing developers to control which files should trigger version changes when modified. It reflects an understanding of how to leverage the TLLV framework effectively for customized data processing workflows.

The other options focus on different aspects of TLLV customization but do not provide the same level of control as the selected answer. A feature like tllvIncludeDeps, while useful for managing dependencies, doesn't specifically allow for granular file path management like tllvFiles does. Setting tllv to false would disable TLLV entirely, which does not customize it