0.5.2

0.5.2 (2021-08-03)

Compatible with Immuta version >=2021.1.2

Added

• Ability to search by data source schema when bulk deleting or tagging data sources

Fixed

• Bug preventing remote columns from persisting after a column is tagged
• Bug that forced data source dictionary updates when tagging because comparisons were failing
• Bug preventing correct evaluation of the schema evolution status check for Snowflake remote databases
• Data source deletion logic to account for updated API response to allow for hard deletes

0.5.1

0.5.1 (2021-06-25)

Compatible with Immuta version >=2021.1.2

Added

• Support for Snowflake handler. Users can now enroll Snowflake data sources and enable Secure Views on those data sources.

0.5.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.

0.4.0

0.4.0 (2020-03-01)

Compatible with Immuta version >=2020.3.4

Added

• Ability to control schema evolution settings for a remote database/server from configuration.

Changed

• Immuta data source and query engine table name truncation character limits. Limits for both are now set to 255 to
  align with the accepted limits by the Immuta application. Users with previously truncated data source or query engine
  table names should delete and re-enroll those data sources to enroll the full names.

0.3.0

0.3.0 (2020-12-11)

Compatible with Immuta version >=2020.3.2

Added

• BREAKING CHANGE: Allow for automatic subscription parameter to be read from subscription policy configs. Automatic subscription for subscription policies defaults to True to stay in line with the Immuta API and UI.

Fixed

• Change iam parameter for PolicyGroup to optional to address Immuta API no longer returning the iam parameter
  when getting policies.

0.2.0

Release 0.2.0

0.1.0

Bumped version to 0.1.0

0.0.7

Bumped version to 0.0.7

0.0.6

Bumped version to 0.0.6

0.0.5

bumped version to 0.0.5