From 3e23c7532b662b793333ea5f84fcbd0337c05b97 Mon Sep 17 00:00:00 2001 From: Kris Date: Fri, 4 Oct 2024 21:41:01 +0300 Subject: [PATCH] fix(metadata-service): Pass editableDatasetNameEnabled feature flag to the config. (#11391) Co-authored-by: Kristina Kurshakova --- .../configuration/src/main/resources/application.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/metadata-service/configuration/src/main/resources/application.yaml b/metadata-service/configuration/src/main/resources/application.yaml index 3177a97125194..24764b512c232 100644 --- a/metadata-service/configuration/src/main/resources/application.yaml +++ b/metadata-service/configuration/src/main/resources/application.yaml @@ -436,6 +436,7 @@ featureFlags: businessAttributeEntityEnabled: ${BUSINESS_ATTRIBUTE_ENTITY_ENABLED:false} # Enables business attribute entity which can be associated with field of dataset dataContractsEnabled: ${DATA_CONTRACTS_ENABLED:true} # Enables the Data Contracts feature (Tab) in the UI showSeparateSiblings: ${SHOW_SEPARATE_SIBLINGS:false} # If turned on, all siblings will be separated with no way to get to a "combined" sibling view + editableDatasetNameEnabled: ${EDITABLE_DATASET_NAME_ENABLED:false} # Enables the ability to edit the dataset name in the UI entityChangeEvents: enabled: ${ENABLE_ENTITY_CHANGE_EVENTS_HOOK:true}