Skip to content

Commit dbcc11d

Browse files
authored
Task ReadMe changes (GoogleCloudPlatform#1420)
* Readme update * fix queue name
1 parent 3400342 commit dbcc11d

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

tasks/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22

33
This sample demonstrates using the Cloud Tasks client library.
44

5-
`CreateHTTPTask.java` constructs a task with an HTTP target and pushes it
5+
`CreateHttpTask.java` constructs a task with an HTTP target and pushes it
66
to your queue.
77

8-
`CreateHTTPTask.java` constructs a task with an HTTP target and OIDC token and
8+
`CreateHttpTask.java` constructs a task with an HTTP target and OIDC token and
99
pushes it to your queue.
1010

1111
## Initial Setup
@@ -39,7 +39,7 @@ Then the queue ID, as specified at queue creation time. Queue IDs already
3939
created can be listed with `gcloud beta tasks queues list`.
4040

4141
```
42-
export QUEUE_ID=my-queue
42+
export QUEUE_ID=<QUEUE_NAME>
4343
```
4444

4545
And finally the location ID, which can be discovered with
@@ -52,7 +52,7 @@ location is "us-central1").
5252
export LOCATION_ID=<YOUR_ZONE>
5353
```
5454

55-
### Using HTTP Push Queues
55+
### Creating Tasks with HTTP Targets
5656

5757
Set an environment variable for the endpoint to your task handler. This is an
5858
example url:

tasks/src/main/java/com/example/task/CreateHttpTaskWithToken.java

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ public static void main(String[] args) throws Exception {
3838
try (CloudTasksClient client = CloudTasksClient.create()) {
3939
// Variables provided by the system variables.
4040
// projectId = "my-project-id";
41-
// queueName = "my-appengine-queue";
41+
// queueName = "my-queue";
4242
// location = "us-central1";
4343
// url = "https://example.com/taskhandler";
4444
String payload = "hello";

0 commit comments

Comments
 (0)