Skip to content

Commit

Permalink
fix incorrect query param in deployment logs endpoint docs (#13620)
Browse files Browse the repository at this point in the history
* Deployment logs endpoint uses a continuationToken query param instead of nextToken
  • Loading branch information
nyobe authored Dec 18, 2024
1 parent 5036d79 commit bdbdb6e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions content/docs/pulumi-cloud/deployments/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -1177,7 +1177,7 @@ The `token` is a string that contains the `job`, `offset` and `step` of the next

The following query parameters are available:

* **nextToken**: A string returned by the previous response, that can be used to get the next set of logs.
* **continuationToken**: The `nextToken` value from the previous response, that can be used to get the next set of logs.

##### Example

Expand Down Expand Up @@ -1227,12 +1227,12 @@ Response
}
```

Following request (using `nextToken`)
Following request (using the returned `nextToken`)

```shell
curl -XGET -H "Content-Type: application/json" \
-H "Authorization: token $PULUMI_ACCESS_TOKEN" \
--location "https://api.pulumi.com/api/stacks/my-org/aws-ts-s3-folder/dev/deployments/6b1ec06b-4f41-4cce-a7c9-13ceded14db2/logs?nextToken=0.2.1"
--location "https://api.pulumi.com/api/stacks/my-org/aws-ts-s3-folder/dev/deployments/6b1ec06b-4f41-4cce-a7c9-13ceded14db2/logs?continuationToken=0.2.1"
```

Response
Expand Down

0 comments on commit bdbdb6e

Please sign in to comment.