From d44c241ac64a9589fa9289756092c8b271bcaf59 Mon Sep 17 00:00:00 2001 From: Andrew Tsao <45043255+AndrewRTsao@users.noreply.github.com> Date: Wed, 8 May 2024 04:36:54 -0400 Subject: [PATCH] Changing to (#4853) Clarifying to make the callout less confusing and clear that we're not referring to a global location --- docs/docs/reference/connectors/athena.md | 2 +- docs/docs/reference/connectors/azure.md | 2 +- docs/docs/reference/connectors/bigquery.md | 2 +- docs/docs/reference/connectors/gcs.md | 2 +- docs/docs/reference/connectors/motherduck.md | 2 +- docs/docs/reference/connectors/mysql.md | 2 +- docs/docs/reference/connectors/postgres.md | 2 +- docs/docs/reference/connectors/redshift.md | 2 +- docs/docs/reference/connectors/s3.md | 2 +- docs/docs/reference/connectors/salesforce.md | 2 +- docs/docs/reference/connectors/snowflake.md | 2 +- docs/docs/reference/project-files/sources.md | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/docs/reference/connectors/athena.md b/docs/docs/reference/connectors/athena.md index ac34947cdf6..32ed3e84742 100644 --- a/docs/docs/reference/connectors/athena.md +++ b/docs/docs/reference/connectors/athena.md @@ -63,7 +63,7 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/azure.md b/docs/docs/reference/connectors/azure.md index 39b3c45210e..26ce8d6cd7b 100644 --- a/docs/docs/reference/connectors/azure.md +++ b/docs/docs/reference/connectors/azure.md @@ -102,6 +102,6 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/bigquery.md b/docs/docs/reference/connectors/bigquery.md index 9c2848310b9..9e6d89f42ff 100644 --- a/docs/docs/reference/connectors/bigquery.md +++ b/docs/docs/reference/connectors/bigquery.md @@ -48,7 +48,7 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/gcs.md b/docs/docs/reference/connectors/gcs.md index ebbbdd6bb22..015613c52c1 100644 --- a/docs/docs/reference/connectors/gcs.md +++ b/docs/docs/reference/connectors/gcs.md @@ -66,7 +66,7 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/motherduck.md b/docs/docs/reference/connectors/motherduck.md index 7b1d9cd2f28..1ca27252ff0 100644 --- a/docs/docs/reference/connectors/motherduck.md +++ b/docs/docs/reference/connectors/motherduck.md @@ -94,6 +94,6 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: \ No newline at end of file diff --git a/docs/docs/reference/connectors/mysql.md b/docs/docs/reference/connectors/mysql.md index dbb03e2b26a..4b341e698a1 100644 --- a/docs/docs/reference/connectors/mysql.md +++ b/docs/docs/reference/connectors/mysql.md @@ -78,6 +78,6 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: \ No newline at end of file diff --git a/docs/docs/reference/connectors/postgres.md b/docs/docs/reference/connectors/postgres.md index 718bf3a12c6..ad903543c9e 100644 --- a/docs/docs/reference/connectors/postgres.md +++ b/docs/docs/reference/connectors/postgres.md @@ -76,6 +76,6 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: \ No newline at end of file diff --git a/docs/docs/reference/connectors/redshift.md b/docs/docs/reference/connectors/redshift.md index 63ea1f0ee54..5a1b120c5f9 100644 --- a/docs/docs/reference/connectors/redshift.md +++ b/docs/docs/reference/connectors/redshift.md @@ -63,7 +63,7 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/s3.md b/docs/docs/reference/connectors/s3.md index 458db3a1af2..8f85fca3f10 100644 --- a/docs/docs/reference/connectors/s3.md +++ b/docs/docs/reference/connectors/s3.md @@ -68,7 +68,7 @@ Note that you must `cd` into the Git repository that your project was deployed f :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/connectors/salesforce.md b/docs/docs/reference/connectors/salesforce.md index 18283bab802..92ccbb194cf 100644 --- a/docs/docs/reference/connectors/salesforce.md +++ b/docs/docs/reference/connectors/salesforce.md @@ -79,6 +79,6 @@ signing. :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: \ No newline at end of file diff --git a/docs/docs/reference/connectors/snowflake.md b/docs/docs/reference/connectors/snowflake.md index 3f098acaf90..dc4888075b9 100644 --- a/docs/docs/reference/connectors/snowflake.md +++ b/docs/docs/reference/connectors/snowflake.md @@ -62,7 +62,7 @@ Note that you must first `cd` into the Git repository that your project was depl :::tip Did you know? -If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. +If you've configured credentials locally already (in your `/.env` file), you can use `rill env push` to [push these credentials](/build/credentials/credentials.md#rill-env-push) to your Rill Cloud project. This will allow other users to retrieve / reuse the same credentials automatically by running `rill env pull`. ::: diff --git a/docs/docs/reference/project-files/sources.md b/docs/docs/reference/project-files/sources.md index 5bab333ff1e..60d0a64910f 100644 --- a/docs/docs/reference/project-files/sources.md +++ b/docs/docs/reference/project-files/sources.md @@ -34,7 +34,7 @@ Files that are *nested at any level* under your native `sources` directory will - _`duckdb`_ - use the [embedded DuckDB](../olap-engines/duckdb.md) engine to submit a DuckDB-supported native [SELECT](https://duckdb.org/docs/sql/statements/select.html) query (should be used in conjunction with the `sql` property) **`type`** - — _Deprecated_ but preserves a legacy alias to `connector`. Can be used instead to specify the source connector, instead of the resource type (see above), **only** if the source YAML file belongs in the `/sources/` directory (preserved primarily for backwards compatibility). + — _Deprecated_ but preserves a legacy alias to `connector`. Can be used instead to specify the source connector, instead of the resource type (see above), **only** if the source YAML file belongs in the `/sources/` directory (preserved primarily for backwards compatibility). **`uri`** — Refers to the URI of the remote connector you are using for the source. Rill also supports glob patterns as part of the URI for S3 and GCS _(required for type: http, s3, gcs)_.