other xyz references

macros/run_sp_create_prod_clone.sql

@@ -1,6 +1,6 @@
 {% macro run_sp_create_prod_clone() %}
 {% set clone_query %}
-call xyz._internal.create_prod_clone('xyz', 'xyz_dev', 'internal_dev');
+call aurora._internal.create_prod_clone('aurora', 'aurora_dev', 'internal_dev');
 {% endset %}
 
 {% do run_query(clone_query) %}

macros/tags/add_database_or_schema_tags.sql

@@ -1,10 +1,10 @@
 {% macro add_database_or_schema_tags() %}
     {{ set_database_tag_value(
         'BLOCKCHAIN_NAME',
-        'xyz'
+        'AURORA'
     ) }}
       {{ set_database_tag_value(
         'BLOCKCHAIN_TYPE',
-        'IBC'
+        'EVM'
     ) }}
 {% endmacro %}

models/descriptions/__overview__.md

@@ -1,10 +1,10 @@
 {% docs __overview__ %}
 
-# Welcome to the Flipside Crypto xyz Models Documentation
+# Welcome to the Flipside Crypto Aurora Models Documentation
 
 ## **What does this documentation cover?**
-The documentation included here details the design of the xyz
- tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/) For more information on how these models are built, please see [the github repository.](https://github.com/flipsideCrypto/xyz-models/)
+The documentation included here details the design of the Aurora
+ tables and views available via [Flipside Crypto.](https://flipsidecrypto.xyz/) For more information on how these models are built, please see [the github repository.](https://github.com/flipsideCrypto/aurora-models/)
 
 ## **How do I use these docs?**
 The easiest way to navigate this documentation is to use the Quick Links below. These links will take you to the documentation for each table, which contains a description, a list of the columns, and other helpful information.
@@ -17,7 +17,7 @@ There is more information on how to use dbt docs in the last section of this doc
 
 **Click on the links below to jump to the documentation for each schema.**
 
-### Core Tables (`xyz`.`CORE`.`<table_name>`)
+### Core Tables (`AURORA`.`CORE`.`<table_name>`)
 
 **Dimension Tables:**
 
@@ -33,8 +33,7 @@ There is more information on how to use dbt docs in the last section of this doc
 
 ## **Data Model Overview**
 
-The xyz
- models are built a few different ways, but the core fact tables are built using three layers of sql models: **bronze, silver, and gold (or core).**
+The Aurora models are built a few different ways, but the core fact tables are built using three layers of sql models: **bronze, silver, and gold (or core).**
 
 - Bronze: Data is loaded in from the source as a view
 - Silver: All necessary parsing, filtering, de-duping, and other transformations are done here
@@ -68,7 +67,7 @@ Note that you can also right-click on models to interactively filter and explore
 - [Flipside](https://flipsidecrypto.xyz/)
 - [Velocity](https://app.flipsidecrypto.com/velocity?nav=Discover)
 - [Tutorials](https://docs.flipsidecrypto.com/our-data/tutorials)
-- [Github](https://github.com/FlipsideCrypto/xyz-models)
+- [Github](https://github.com/FlipsideCrypto/aurora-models)
 - [What is dbt?](https://docs.getdbt.com/docs/introduction)
 
 {% enddocs %}

models/sources.yml

@@ -2,7 +2,7 @@ version: 2
 
 sources:
   - name: crosschain
-    database: "{{ 'crosschain' if target.database == 'xyz' else 'crosschain_dev' }}"
+    database: "{{ 'crosschain' if target.database == 'AURORA' else 'crosschain_dev' }}"
     schema: core
     tables:
       - name: dim_date_hours

profiles.yml

@@ -5,7 +5,7 @@ aurora:
       type: snowflake
       account: "{{ env_var('ACCOUNT') }}"
       user: "{{ env_var('USER') }}"
-      password: "{{ env_var('PASSWORD') }}"
+      authenticator: externalbrowser
       role: "{{ env_var('ROLE') }}"
       schema: "{{ env_var('SCHEMA') }}"
       region: "{{ env_var('REGION') }}"
@@ -17,7 +17,7 @@ aurora:
       type: snowflake
       account: "{{ env_var('ACCOUNT') }}"
       user: "{{ env_var('USER') }}"
-      password: "{{ env_var('PASSWORD') }}"
+      authenticator: externalbrowser
       role: "{{ env_var('ROLE') }}"
       schema: "{{ env_var('SCHEMA') }}"
       region: "{{ env_var('REGION') }}"