Deleting Your Organization
Note: In order to delete your organization, you have to be an Owner of the organization.
⛔️ This will permanently delete your organization. Please be careful.
Delete the Org in Y42 V1 - Step by Step:
- In the main navigation, click the Admin tab.
- Click the Delete Organization tab on the left.
- Click Delete Organization, if you're sure you want to permanently delete it. All users will lose access to all resources.
Delete remaining Y42 V1 related datasets
If you are planning to migrate and/or are already utilizing the Y42 version 2 platform (V2), we highly recommend creating a new Google Cloud project specifically for your V2 organization. By doing this, you can effectively segregate any assets associated with Y42 V1 and Y42 V2.
🚨 It is crucial that you do not delete datasets following the provided syntax if you are using Y42 V2:
y42_[space_name]_[uniqueID] (e.g. y42_testspace_6dab88f71a504321b8cc57221b1a091c) [org_name]_public_[space_name]_main (e.g. testorg_public_testspace_main)
Datasets following this syntax contain tables and views that support your V2 spaces. They are crucial for supporting Y42 V2!
If you are migrating to Y42 version 2 and want to clean up datasets related to the Y42 version 1 platform (V1) and remove them from both BigQuery and Google Cloud Storage, you have the option to delete the entire project linked to the V1 platform.
The deletion of datasets in BigQuery can not be reversed. Please assure yourself before you are deleting datasets.
Back-up V1 UI models
If you wish to create a backup of your data lineage and models from V1, you can easily do so by following these steps:
In Y42 V1, UI models can be downloaded as JSON files, which encompass all the configurations of a Y42 UI model. These JSON files can then be imported into Y42 V2, allowing for the replication of models from V1 to V2. For SQL models created in Y42 V1, you can conveniently copy and paste them directly into a text document for safekeeping.
Download a snapshot of your data lineage as a PNG
- Go to your data lineage
- Download the data lineage as PNG
Download your UI model as JSON file
- Go to the UI model you want to back-up as JSON file
- Click on the “Download Model File” in the menu bar
Identify Back-Up and Y42 V1 related datasets
BigQuery datasets linked to Y42 V1 have the following name structure:
views_y42_[uniqueID](e.g. views_y42_abc924e2_defg_41c4_b122_a50ee9591c21)y42_[uniqueID](e.g. y42_abc924e2_defg_41c4_b122_a50ee9591c21)datos_[uniqueID](e.g. datos_abc924e2_defg_41c4_b122_a50ee9591c21)datos_view_y42[uniqueID](e.g. datos_view_y42_abc924e2_defg_41c4_b122_a50ee9591c21)
Google Cloud Storage buckets linked to Y42 V1 have the following name structure:
datos_integration_[uniqueID](e.g. datos_integration_y42_abc924e2_defg_41c4_b122_a50ee9591c21)datos_target_integration_[uniqueID](e.g. datos_target_integration_y42_abc924e2_defg_41c4_b122_a50ee9591c21)y42_[uniqueID](e.g. y42_abc924e2_defg_41c4_b122_a50ee9591c21)
The user is free to just let these old datasets live in his GCP project as a reference point or back up them by copying them into dedicated other datasets or CSV downloads via the GCP admin console (see e.g. this tutorial: https://blog.coupler.io/how-to-copy-bigquery-table/ )
Delete Y42 V1 related data sets
♻️ Datasets and Cloud Storage objects that are associated with “old” Y42 V1 instances are not necessary for the “new” Y42 V2 space to function properly. It is possible to clean them up manually at the users own discretion and care without compromising the “new” Y42 V2 space.