Merge pull request #91 from get-select/3.0.1

Release 3.0.1

.changes/3.0.1.md

@@ -0,0 +1,9 @@
+## dbt-snowflake-monitoring 3.0.1 - March 01, 2023
+
+### Fixes
+
+- Fix dbt_cloud_url var ([#90](https://github.com/get-select/dbt-snowflake-monitoring/pull/90))
+
+### Contributors
+- [@vinooganesh](https://github.com/vinooganesh) (Fixes)
+

CHANGELOG.md

@@ -5,6 +5,16 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
+## dbt-snowflake-monitoring 3.0.1 - March 01, 2023
+
+### Fixes
+
+- Fix dbt_cloud_url var ([#90](https://github.com/get-select/dbt-snowflake-monitoring/pull/90))
+
+### Contributors
+- [@vinooganesh](https://github.com/vinooganesh) (Fixes)
+
+
 ## dbt-snowflake-monitoring 3.0.0 - February 26, 2023
 After attempting to use only query comments or query tags in versions 1 and 2, we've learned we actually need both. The reasons for that are:
 * The `is_incremental` macro is only available from within the query tag dbt context, and is needed to determine whether a model run is incremental or not.

README.md

@@ -15,7 +15,7 @@ grant imported privileges on database snowflake to role your_dbt_role_name;
 ```yaml
 packages:
   - package: get-select/dbt_snowflake_monitoring
-    version: 3.0.0
+    version: 3.0.1
 ```
 
 3. To attribute costs to individual models via the `dbt_metadata` column in the `query_history_enriched` model, query comments and tags are added to all dbt-issued queries. Both query comments and tags are needed to collect the required metadata for the `dbt_queries` model. To add the query tags follow one of these two options:

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'dbt_snowflake_monitoring'
-version: '3.0.0'
+version: '3.0.1'
 config-version: 2
 
 profile: dbt_snowflake_monitoring