0.9.0

New Features

MS Graph and Helping to Support Expert and Owner Lookup

• For Purview users, introduced a utility function for the MS Graph, making it easier to look up user object ids.
  • PurviewClient.msgraph.upn_to_id
  • PurviewClient.msgraph.email_to_id
• After introducing these utility functions, the ExcelReader.parse_bulk_entities method takes a contacts_func.
  • The contacts_func parameter takes a function and will be executed for every contact provided in the experts and owners columns.

AtlasObjectId to Avoid Updating Existing Required Relationships

• The ExcelReader.parse_bulk_entities now supports using an AtlasObjectId as a reference in the [Relationship].

  • For example, if you wanted to reference an existing entity without uploading it in the BulkEntities tab, you would use...
  • AtlasObjectId(guid:xx-yy-zz) or AtlasObjectId(typeName:someType qualifiedName:someQualifiedName).
  • This would be the value inside of a [Relationship] xyz column where xyz is the relationship attribute name.
  • This is really useful when you have a required relationship (like azure_sql_schema for an azure_sql_table) that also has a required relationship.
  • This lets you reference only the first dependency and you don't risk changing anything like the name or having to deal with required types.

• The PurviewClient and AtlasClient now have a glossary property which supports many of the glossary endpoints.

• In addition a PurviewGlossaryTerm and an AtlasGlossaryTerm class are provided.

  • PurviewGlossaryTerm supports term hierarchy with the add_hierarchy method.

• For current Atlas users, added support for defining businessMetadataDefs.

• For current Atlas users, added support for the label endpoints by introducing:

  • AtlasClient.update_entity_labels
  • AtlasClient.delete_entity_labels

• For current Atlas users (and one day Purview users too), added support for customAttributes in the excel upload by using a column header [custom] myAttribute.

Breaking Changes

• Added a deprecation warning around the AtlasClient glossary methods. Users should migrate to AtlasClient.glossary or PurviewClient.glossary.