DataOps Bundled Feature Flags

Bundled feature flags in DataOps.live provides a structured and efficient approach to managing and deploying features that include behavioral changes that may break backward compatibility. When activated, bundled feature flags impact all the components of the Dataops.live platform associated with that particular bundle.

Why to use bundled feature flags?

Bundled feature flags offer control and flexibility, reducing complexity and providing users with a more efficient way to adopt and test new features while minimizing risks. Instead of toggling each feature individually, you can control multiple ones as a group, making activating or deactivating them easier by simply using the variable DATAOPS_ENABLE_BEHAVIOR_CHANGE_BUNDLE.

Feature flags facilitate efficient testing of sets of features. You can toggle on or off entire bundles during testing phases, streamlining the testing process. If any bundled features cause issues or conflicts, you can quickly revert the entire bundle, reducing the risk of unexpected problems affecting your operations.

See Project variables for information about where to set this variable and what value to use to activate a specific bundled feature flag.

DataOps.live bundles

Here is a list of the behavioral changes in all the released bundled feature flags.

Bundle 2023_08

Empty YAML files

Previously, empty YAML files or empty lists in YAML files in your configuration cause compile errors.

With the feature flag activated, the Snowflake Object Lifecycle Engine (SOLE) handles empty lists and null values identically.

Revoking grants

Previously, SOLE does not revoke grants on the privileges of Snowflake objects when an empty list is provided.

With the feature flag activated, you can revoke all privileges with an empty grants: list.

SOLE in feature branch

Previously, when SOLE runs in a feature branch with DATAOPS_FEATURE_BRANCH_NONDB_ENV_NAME set to DEV, account-level resources are NOT reused from the DEV environment and are created for each feature branch. And when the feature branch teardown job runs, all account-level resources (apart from the main DB) are dropped from the DEV environment.

With the feature flag activated, SOLE doesn't create DEV resources in a feature branch, and, more importantly, it doesn't teardown DEV resources in a feature branch.