Aspire Data Warehouse Design Artefacts Deprecation Standards

urn:js:virtue:aspire:standard:26.1

TL;DR

Dropping an obsolete object in Snowflake mandates the associated design artefacts to be in sync with Snowflake hence requires deprecation.

Definition

An object can become obsolete in Aspire due to various reasons like users moving to a new data product, objects created for POC purposes that has to be cleared etc.. In such cases, product owners & data architects will identify objects to be dropped from snowflake. If a decision has been made by product ownership to drop an object in snowflake, then it is recommended to clear all the design artefacts associated with the object.Following flow diagram covers the tasks to follow for design artefact deprecation.

Design Artefacts Deprecation Flow

Key Points

1) Design artefacts deprecation should go hand in hand with SF object deletion. Combined Jira ticket for DA and Engineering task is recommended to avoid any inconsistencies. 2) Objects must be deprecated and dropped only with necessary approval from product ownership. 3) It is recommended to allow trial period of upto 3 weeks between stakeholder communication and actual implementation. In this period in order to uncover any unpredicted/hidden dependencies it is recommended to rename the object to OBJECT_NAME_«/TOBEDEPRECATED/». Also update the Alation deprecation flag to inform users that the object is flagged for deprecation.