cloud-cli beta and SL GA launch

website/docs/reference/commands/clone.md

@@ -21,7 +21,7 @@ The `clone` command is useful for:
 dbt clone --state path/to/artifacts
 
 # clone one_specific_model of my models from specified state to my target schema(s)
-dbt clone --select one_specific_model --state path/to/artifacts
+dbt clone --select "one_specific_model" --state path/to/artifacts
 
 # clone all of my models from specified state to my target schema(s) and recreate all pre-existing relations in the current target
 dbt clone --state path/to/artifacts --full-refresh

website/docs/reference/commands/compile.md

@@ -29,15 +29,15 @@ This will log the compiled SQL to the terminal, in addition to writing to the `t
 For example:
 
 ```bash
-dbt compile --select stg_payments
+dbt compile --select "stg_payments"
 dbt compile --inline "select * from {{ ref('raw_orders') }}"
 ```
 
 returns the following:
 
 
 ```bash
-dbt compile --select stg_orders
+dbt compile --select "stg_orders"
 21:17:09 Running with dbt=1.5.0-b5
 21:17:09 Found 5 models, 20 tests, 0 snapshots, 0 analyses, 425 macros, 0 operations, 3 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
 21:17:09

website/docs/reference/commands/list.md

@@ -8,6 +8,7 @@ id: "list"
 The `dbt ls` command lists resources in your dbt project. It accepts selector arguments that are similar to those provided in [dbt run](/reference/commands/run). `dbt list` is an alias for `dbt ls`. While `dbt ls` will read your [connection profile](/docs/core/connect-data-platform/connection-profiles) to resolve [`target`](/reference/dbt-jinja-functions/target)-specific logic, this command will not connect to your database or run any queries.
 
 ### Usage
+
 ```
 dbt ls
      [--resource-type {model,source,seed,snapshot,metric,test,exposure,analysis,default,all}]
@@ -85,7 +86,7 @@ $ dbt ls --select snowplow.* --output json --output-keys "name resource_type des
 <VersionBlock firstVersion="1.5">
 
 ```
-$ dbt ls --select snowplow.* --output json --output-keys name resource_type description
+$ dbt ls --select snowplow.* --output json --output-keys "name resource_type description"
 {"name": "snowplow_events", "description": "This is a pretty cool model",  ...}
 {"name": "snowplow_page_views", "description": "This model is even cooler",  ...}
 ...

website/docs/reference/commands/seed.md

@@ -12,7 +12,7 @@ The `dbt seed` command will load `csv` files located in the `seed-paths` directo
 Specific seeds can be run using the `--select` flag to `dbt seed`. Example:
 
 ```
-$ dbt seed --select country_codes
+$ dbt seed --select "country_codes"
 Found 2 models, 3 tests, 0 archives, 0 analyses, 53 macros, 0 operations, 2 seed files
 
 14:46:15 | Concurrency: 1 threads (target='dev')

website/docs/reference/commands/show.md

@@ -16,7 +16,7 @@ The results of the preview query are not materialized in the data warehouse, or
 Example:
 
 ```
-dbt show --select model_name.sql
+dbt show --select "model_name.sql"
 ```
 or
 ```
@@ -26,7 +26,7 @@ dbt show --inline "select * from {{ ref('model_name') }}"
 The following is an example of `dbt show` output for a model named `stg_orders`:
 
 ```bash
-dbt show --select stg_orders
+dbt show --select "stg_orders"
 21:17:38 Running with dbt=1.5.0-b5
 21:17:38 Found 5 models, 20 tests, 0 snapshots, 0 analyses, 425 macros, 0 operations, 3 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
 21:17:38
@@ -46,7 +46,7 @@ dbt show --select stg_orders
 For example, if you've just built a model that has a failing test, you can quickly preview the test failures right in the terminal, to find values of `id` that are duplicated:
 
 ```bash
-$ dbt build -s my_model_with_duplicates
+$ dbt build -s "my_model_with_duplicates"
 13:22:47 Running with dbt=1.5.0
 ...
 13:22:48 Completed with 1 error and 0 warnings:
@@ -58,7 +58,7 @@ $ dbt build -s my_model_with_duplicates
 13:22:48
 13:22:48 Done. PASS=1 WARN=0 ERROR=1 SKIP=0 TOTAL=2
 
-$ dbt show -s unique_my_model_with_duplicates_id
+$ dbt show -s "unique_my_model_with_duplicates_id"
 13:22:53 Running with dbt=1.5.0
 13:22:53 Found 4 models, 2 tests, 0 snapshots, 0 analyses, 309 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
 13:22:53

website/docs/reference/commands/source.md

@@ -20,10 +20,10 @@ By default, `dbt source freshness` will calculate freshness information for all
 
 ```bash
 # Snapshot freshness for all Snowplow tables:
-$ dbt source freshness --select source:snowplow
+$ dbt source freshness --select "source:snowplow"
 
 # Snapshot freshness for a particular source table:
-$ dbt source freshness --select source:snowplow.event
+$ dbt source freshness --select "source:snowplow.event"
 ```
 
 ### Configuring source freshness output

website/docs/reference/commands/test.md

@@ -10,22 +10,22 @@ The tests to run can be selected using the `--select` flag discussed [here](/ref
 
 ```bash
 # run tests for one_specific_model
-dbt test --select one_specific_model
+dbt test --select "one_specific_model"
 
 # run tests for all models in package
-dbt test --select some_package.*
+dbt test --select "some_package.*"
 
 # run only tests defined singularly
-dbt test --select test_type:singular
+dbt test --select "test_type:singular"
 
 # run only tests defined generically
-dbt test --select test_type:generic
+dbt test --select "test_type:generic"
 
 # run singular tests limited to one_specific_model
-dbt test --select one_specific_model,test_type:singular
+dbt test --select "one_specific_model,test_type:singular"
 
 # run generic tests limited to one_specific_model
-dbt test --select one_specific_model,test_type:generic
+dbt test --select "one_specific_model,test_type:generic"
 ```
 
 For more information on writing tests, see the [Testing Documentation](/docs/build/tests).

website/docs/reference/dbt_project.yml.md

@@ -11,6 +11,8 @@ By default, dbt will look for `dbt_project.yml` in your current working director
 
 By default, dbt will look for `dbt_project.yml` in your current working directory and its parents, but you can set a different directory using the `--project-dir` flag or the `DBT_PROJECT_DIR` environment variable.
 
+Starting from dbt v1.5 and higher, you can specify your dbt Cloud project ID in the `dbt_project.yml` file using the `dbt-cloud` config, which doesn't require validation or storage in the project config class. To find your project ID, check your dbt Cloud project URL, such as `https://cloud.getdbt.com/11/projects/123456`, where the project ID is `123456`.
+
 </VersionBlock>
 
 The following is a list of all available configurations in the `dbt_project.yml` file.
@@ -19,6 +21,9 @@ The following is a list of all available configurations in the `dbt_project.yml`
 dbt uses YAML in a few different places. If you're new to YAML, it would be worth taking the time to learn how arrays, dictionaries and strings are represented.
 :::
 
+
+<VersionBlock firstVersion="1.5">
+
 <File name='dbt_project.yml'>
 
 ```yml
@@ -48,6 +53,10 @@ dbt uses YAML in a few different places. If you're new to YAML, it would be wort
 
 [require-dbt-version](/reference/project-configs/require-dbt-version): version-range | [version-range]
 
+[dbt-cloud](/docs/cloud/cloud-cli-installation):
+  project-id: project_id #Required
+  defer-env-id: 5678 #Optional
+
 [quoting](/reference/project-configs/quoting):
   database: true | false
   schema: true | false
@@ -79,6 +88,77 @@ vars:
     search_order: [packagename]
 
 [restrict-access](/docs/collaborate/govern/model-access): true | false
+
 ```
 
 </File>
+</VersionBlock>
+
+<VersionBlock lastVersion="1.5">
+
+<File name='dbt_project.yml'>
+
+```yml
+[name](/reference/project-configs/name): string
+
+[config-version](/reference/project-configs/config-version): 2
+[version](/reference/project-configs/version): version
+
+[profile](/reference/project-configs/profile): profilename
+
+[model-paths](/reference/project-configs/model-paths): [directorypath]
+[seed-paths](/reference/project-configs/seed-paths): [directorypath]
+[test-paths](/reference/project-configs/test-paths): [directorypath]
+[analysis-paths](/reference/project-configs/analysis-paths): [directorypath]
+[macro-paths](/reference/project-configs/macro-paths): [directorypath]
+[snapshot-paths](/reference/project-configs/snapshot-paths): [directorypath]
+[docs-paths](/reference/project-configs/docs-paths): [directorypath]
+[asset-paths](/reference/project-configs/asset-paths): [directorypath]
+
+[target-path](/reference/project-configs/target-path): directorypath
+[log-path](/reference/project-configs/log-path): directorypath
+[packages-install-path](/reference/project-configs/packages-install-path): directorypath
+
+[clean-targets](/reference/project-configs/clean-targets): [directorypath]
+
+[query-comment](/reference/project-configs/query-comment): string
+
+[require-dbt-version](/reference/project-configs/require-dbt-version): version-range | [version-range]
+
+[quoting](/reference/project-configs/quoting):
+  database: true | false
+  schema: true | false
+  identifier: true | false
+
+models:
+  [<model-configs>](/reference/model-configs)
+
+seeds:
+  [<seed-configs>](/reference/seed-configs)
+
+snapshots:
+  [<snapshot-configs>](/reference/snapshot-configs)
+
+sources:
+  [<source-configs>](source-configs)
+
+tests:
+  [<test-configs>](/reference/test-configs)
+
+vars:
+  [<variables>](/docs/build/project-variables)
+
+[on-run-start](/reference/project-configs/on-run-start-on-run-end): sql-statement | [sql-statement]
+[on-run-end](/reference/project-configs/on-run-start-on-run-end): sql-statement | [sql-statement]
+
+[dispatch](/reference/project-configs/dispatch-config):
+  - macro_namespace: packagename
+    search_order: [packagename]
+
+[restrict-access](/docs/collaborate/govern/model-access): true | false
+
+```
+
+</File>
+
+</VersionBlock>

website/docs/reference/global-configs/command-line-flags.md

@@ -4,60 +4,91 @@ id: "command-line-flags"
 sidebar: "Command line flags"
 ---
 
-Command line (CLI) flags immediately follow `dbt` and precede your subcommand. When set, CLI flags override environment variables and profile configs.
+For consistency, command line (CLI) flags should come right after the `dbt` prefix and its subcommands. This includes "global" flags (supported for all commands). When set, CLI flags override environment variables and profile configs. 
 
-Use this non-boolean config structure, replacing  `<THIS-CONFIG>` with the config you are enabling or disabling, `<SETTING>` with the new setting for the config, and `<SUBCOMMAND>`  with the command this config applies to:
+For example, instead of using:
+
+```bash
+dbt --no-populate-cache run
+```
+
+You should use:
+
+```bash
+dbt run --no-populate-cache
+```
+
+Historically, passing flags (such as "global flags") _before_ the subcommand is a legacy functionality that dbt Labs can remove at any time. We do not support using the same flag before and after the subcommand. 
+
+<Tabs>
+
+<TabItem value="nonboolean" label="Non-boolean config">
+
+Use this non-boolean config structure:
+- Replacing `<SUBCOMMAND>`  with the command this config applies to.
+- `<THIS-CONFIG>` with the config you are enabling or disabling, and
+- `<SETTING>` with the new setting for the config.
 
 <File name='CLI flags'>
 
 
 ```text
 
-$ --<THIS-CONFIG>=<SETTING> <SUBCOMMAND>
+<SUBCOMMAND> --<THIS-CONFIG>=<SETTING> 
 
 ```
 
 </File>
 
-Non-boolean config examples:
+### Example
 
 <File name='CLI flags'>
 
 
 ```text
 
-dbt --printer-width=80 run
-dbt --indirect-selection=eager test
+dbt run --printer-width=80 
+dbt test --indirect-selection=eager
 
 ```
 
 </File>
 
-To turn on boolean configs, you would use the `--<THIS-CONFIG>` CLI flag, and a `--no-<THIS-CONFIG>` CLI flag to turn off boolean configs, replacing `<THIS-CONFIG>` with the config you are enabling or disabling and `<SUBCOMMAND>`  with the command this config applies to.
+</TabItem>
+
+<TabItem value="boolean" label="Boolean config">
+
+To enable or disable boolean configs:
+- Use `<SUBCOMMAND>` this config applies to.
+- Followed by `--<THIS-CONFIG>` to turn it on, or `--no-<THIS-CONFIG>` to turn it off.
+- Replace `<THIS-CONFIG>` with the config you are enabling or disabling
 
-Boolean config structure:
 
 <File name='CLI flags'>
 
 
 ```text
-dbt --<THIS-CONFIG> <SUBCOMMAND>
-dbt --no-<THIS-CONFIG> <SUBCOMMAND>
+dbt <SUBCOMMAND> --<THIS-CONFIG> 
+dbt <SUBCOMMAND> --no-<THIS-CONFIG> 
 
 ```
 
 </File>
 
-Boolean config example:
+### Example
 
 <File name='CLI flags'>
 
 
 ```text
 
-dbt --version-check run
-dbt --no-version-check run
+dbt run --version-check
+dbt run --no-version-check 
 
 ```
 
-</File>
+</File>
+
+</TabItem>
+
+</Tabs>