Updated docs for new wrangler commands

Author: maheshwarip

src/content/docs/pipelines/destinations/r2.mdx

@@ -18,14 +18,14 @@ If this is your first time using Pipelines, follow the instructions in the [get
 To create or update a Pipeline using Wrangler, run the following command in a terminal:
 
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME]
+npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME]
 ```
 
 After running this command, you'll be prompted to authorize Cloudflare Workers Pipelines to create R2 API tokens on your behalf. These tokens are required by your Pipeline. Your Pipeline uses the tokens when loading data into your bucket. You can approve the request through the browser link which will open automatically.
 
 If you prefer not to authenticate this way, you may pass your [R2 API Tokens](/r2/api/s3/tokens/) to Wrangler:
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --access-key-id [ACCESS-KEY-ID] --secret-access-key [SECRET-ACCESS-KEY]
+npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --r2-access-key-id [ACCESS-KEY-ID] --r2-secret-access-key [SECRET-ACCESS-KEY]
 ```
 
 ## Deliver partitioned data
@@ -46,7 +46,7 @@ You can specify an optional prefix for all the output files stored in your speci
 
 To modify the prefix for a Pipeline using Wrangler:
 ```sh
-wrangler pipelines update <pipeline-name> --prefix "test"
+wrangler pipelines update <pipeline-name> --r2-prefix "test"
 ```
 
 All the output records generated by your pipeline will be stored under the prefix "test", and will look like this:

src/content/docs/pipelines/get-started.mdx

@@ -43,14 +43,14 @@ To create a Pipeline using Wrangler, run the following command in a terminal, an
 - The name of the R2 bucket you created in step 1
 
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME]
+npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --batch-max-seconds 5 --compression none
 ```
 
 After running this command, you'll be prompted to authorize Cloudflare Workers Pipelines to create R2 API tokens on your behalf. These tokens are required by your Pipeline. Your Pipeline uses the tokens when loading data into your bucket. You can approve the request through the browser link which will open automatically.
 
 If you prefer not to authenticate this way, you may pass your [R2 API Tokens](/r2/api/s3/tokens/) to Wrangler:
 ```sh
-npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --access-key-id [ACCESS-KEY-ID] --secret-access-key [SECRET-ACCESS-KEY]
+npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --r2-access-key-id [ACCESS-KEY-ID] --r2-secret-access-key [SECRET-ACCESS-KEY]
 ```
 
 When choosing a name for your Pipeline:
@@ -60,6 +60,8 @@ When choosing a name for your Pipeline:
 3. The name cannot contain special characters outside dashes (`-`).
 4. The name must start and end with a letter or a number.
 
+You'll notice that we have set two optional flags while creating the pipeline: `--batch-max-seconds` and `--compression`. We've added these flags to make it faster for you to see the output of your first Pipeline. For production use cases, we recommend keeping the default settings.
+
 Once you create your Pipeline, you will receive a HTTP endpoint which you can post data to. You should see output as shown below:
 
 ```sh output
@@ -68,7 +70,7 @@ Once you create your Pipeline, you will receive a HTTP endpoint which you can po
 ✅ Successfully created pipeline [PIPELINE-NAME] with ID [PIPELINE-ID]
 
 You can now send data to your pipeline with:
-  curl "https://<PIPELINE-ID>.pipelines.cloudflare.com/" -d '[{ ...JSON_DATA... }]'
+  curl "https://<PIPELINE-ID>.pipelines.cloudflare.com/" -d '[{ "foo":"bar }]'
 ```
 
 ## 3. Post data to your pipeline
@@ -87,7 +89,7 @@ Pipelines handle batching the data, so you can continue posting data to the Pipe
 
 ## 4. Verify in R2
 
-Go to the R2 bucket you created in step 1 via [the Cloudflare dashboard](https://dash.cloudflare.com/). You should see a prefix for today's date. Click through, and you will see a file created containing the JSON data you posted in step 3.
+Go to the R2 bucket you created in step 1 via [the Cloudflare dashboard](https://dash.cloudflare.com/). You should see a prefix for today's date. Click through, and you will see a file created containing the JSON data you posted in step 3. You will be able to preview the file, and verify that the data you posted in step 2 is present in the file.
 
 ## Summary
 

src/content/docs/pipelines/sources/http.mdx

@@ -14,7 +14,7 @@ Pipelines support ingesting data via HTTP. When you create a new Pipeline, you'l
 
 
 ```sh
-$ npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --access-key-id [ACCESS-KEY-ID] --secret-access-key [SECRET-ACCESS-KEY]
+$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME]
 
 🌀 Creating pipeline named "[PIPELINE-NAME]"
 ✅ Successfully created pipeline [PIPELINE-NAME] with ID [PIPELINE-ID]
@@ -27,16 +27,16 @@ You can now send data to your pipeline with:
 By default, ingestion via HTTP is turned on for all Pipelines. You can turn it off by setting `--http false` when creating or updating a Pipeline.
 
 ```sh
-$ npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --access-key-id [ACCESS-KEY-ID] --secret-access-key [SECRET-ACCESS-KEY] --http false
+$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --enable-http false
 ```
 
 Ingestion URLs are tied to your Pipeline ID. Turning HTTP off, and then turning it back on, will not change the URL.
 
 ## Authentication
 You can secure your HTTP ingestion endpoint using Cloudflare API tokens. By default, authentication is turned off. To enable authentication, use `--authentication true` while creating or updating a Pipeline.
 
-```
-$ npx wrangler pipelines create [PIPELINE-NAME] --r2 [R2-BUCKET-NAME] --access-key-id [ACCESS-KEY-ID] --secret-access-key [SECRET-ACCESS-KEY] --authentication true
+```sh
+$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --require-http-auth true
 ```
 
 Once authentication is turned on, you will need to include a Cloudflare API token in your request headers.