From 57fd4936c470e4969bf700d8a7e1d9851aeae1e7 Mon Sep 17 00:00:00 2001 From: zturechek Date: Fri, 9 Apr 2021 09:48:41 -0400 Subject: [PATCH] Bump version to 0.5.0 --- Dockerfile | 2 +- fh_immuta_utils/__init__.py | 2 +- release_notes/@vNext.md | 20 -------------------- release_notes/v0.5.0.md | 20 ++++++++++++++++++++ setup.py | 2 +- 5 files changed, 23 insertions(+), 23 deletions(-) create mode 100644 release_notes/v0.5.0.md diff --git a/Dockerfile b/Dockerfile index a5c0e22..af8a023 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,7 +1,7 @@ # Build container conda env FROM python:3.7 -ENV LIBRARY_VERSION 0.4.0 +ENV LIBRARY_VERSION 0.5.0 RUN pip install "fh-immuta-utils==${LIBRARY_VERSION}" ENTRYPOINT "fh-immuta-utils" diff --git a/fh_immuta_utils/__init__.py b/fh_immuta_utils/__init__.py index 6a9beea..3d18726 100644 --- a/fh_immuta_utils/__init__.py +++ b/fh_immuta_utils/__init__.py @@ -1 +1 @@ -__version__ = "0.4.0" +__version__ = "0.5.0" diff --git a/release_notes/@vNext.md b/release_notes/@vNext.md index 7a308c7..e69de29 100644 --- a/release_notes/@vNext.md +++ b/release_notes/@vNext.md @@ -1,20 +0,0 @@ -# 0.5.0 (2021-03-24) - -## Compatible with Immuta version `<=2020.3.4` - -### Changed -- BREAKING CHANGE: Data source-level tag keys defined in dataset configuration file will match data source names - using Unix shell-style wildcard matching. This aligns with data source schema and table prefix matching used for the - `schemas_to_enroll` and `schemas_to_bulk_enroll` keys. -- BREAKING CHANGE: Data sources will enroll under their original schema name from the remote database in the Query - Engine unless the `query_engine_target_schema` parameter is provided to override in the dataset configuration file. - This aligns with the Immuta UI default value. -- BREAKING CHANGE: Opt-in is now required in the dataset configuration file to prefix Query Engine table names with - the handler and schema using the `prefix_query_engine_names_with_schema` and `prefix_query_engine_names_with_handler` - flags. This aligns with the Immuta UI default values. -- BREAKING CHANGE: The default value for schema monitoring template parameter `query_engine_table_name_format_default` - no longer includes handler and schema prefixes. This aligns with the Immuta UI default value. -### Fixed -- Data source-level tags apply only to data sources created by the dataset configuration file in which they are defined. - This now matches what the documentation originally stated. -- `user_prefix` from dataset configuration files is now being pulled correctly for schema monitoring templating. diff --git a/release_notes/v0.5.0.md b/release_notes/v0.5.0.md new file mode 100644 index 0000000..09edf27 --- /dev/null +++ b/release_notes/v0.5.0.md @@ -0,0 +1,20 @@ +# 0.5.0 (2021-03-24) + +## Compatible with Immuta version `>=2020.3.4` + +### Changed +- BREAKING CHANGE: Data source-level tag keys defined in dataset configuration file will match data source names + using Unix shell-style wildcard matching. This aligns with data source schema and table prefix matching used for the + `schemas_to_enroll` and `schemas_to_bulk_enroll` keys. +- BREAKING CHANGE: Data sources will enroll under their original schema name from the remote database in the Query + Engine unless the `query_engine_target_schema` parameter is provided to override in the dataset configuration file. + This aligns with the Immuta UI default value. +- BREAKING CHANGE: Opt-in is now required in the dataset configuration file to prefix Query Engine table names with + the handler and schema using the `prefix_query_engine_names_with_schema` and `prefix_query_engine_names_with_handler` + flags. This aligns with the Immuta UI default values. +- BREAKING CHANGE: The default value for schema monitoring template parameter `query_engine_table_name_format_default` + no longer includes handler and schema prefixes. This aligns with the Immuta UI default value. +### Fixed +- Data source-level tags apply only to data sources created by the dataset configuration file in which they are defined. + This now matches what the documentation originally stated. +- `user_prefix` from dataset configuration files is now being pulled correctly for schema monitoring templating. diff --git a/setup.py b/setup.py index 755d93b..153b3c9 100644 --- a/setup.py +++ b/setup.py @@ -11,7 +11,7 @@ setup( name=NAME, - version="0.4.0", + version="0.5.0", entry_points={ "console_scripts": ["fh-immuta-utils = fh_immuta_utils.scripts.cli:main_cli"] },