Clickable prototype and test script

1. Sign in and find a project’s failing work

For someone on call, starting the day.

1. On Sign in, click Sign in with Google. Or click Sign in as the break-glass admin, then Sign in on Admin sign-in.
2. You land on the Dashboard. Read Failing jobs and Backlogs at the top; in the demo both are empty. Further down, Queues gives each queue’s failed attempts and what is waiting.
3. Click orders in the Queues table. The queue opens on its Tasks tab: Queue tasks.
4. Click the Failed tab: Failed tasks lists the tasks that failed for good, with Retry all and Delete all.
5. Click the Logs tab: Queue logs shows each attempt. Type a task’s name and click Filter to see only its attempts.
6. Click the Tasks tab, then order-1001: Task shows its call and every attempt with its answer.
7. For a job, go back to the Dashboard and click homepage-check in its Jobs table: Uptime check.

Expected: you reach one task’s attempts from sign-in without choosing a project first, because the dashboard covers every project you may read.

2. Create a queue, then add a task to it

For a developer wiring a new kind of work.

1. In the sidebar, click Queues: Queues.
2. Click Create queue: Create queue.
3. Type a Queue name: lower-case letters, digits and dashes, starting with a letter. It cannot be changed later. Keep the rate limits and retries, or change them, and click Create.
4. The queue’s page opens with a green notice, said once: Saved notice. For a new queue it reads “Created the queue” and its name.
5. Click Create HTTP task in the toolbar: Create a task.
6. Type the URL, pick the HTTP method, add a header, a body or auth if the target needs them, and click Create.

Expected: the task’s page with “Created the task” and its name: Task created. Its crumbs lead back to the queue.

3. Add many tasks from a file, using the sample

For a one-off batch, such as replaying a day’s orders.

1. On Queue tasks, click Create HTTP task, and scroll to From a file at the foot of Create a task.
2. Click Download a sample. It saves cloud-console-tasks-sample.json: two tasks inside { "tasks": [ ... ] }.
3. Open the file and change each task’s url, and anything else: the sample’s tasks call https://example.com/ as soon as they are made. Only url is required, and a file holds up to 50 tasks.
4. Under Tasks file, choose the file, then click Create tasks.

Expected: a status line such as “Created 2 tasks”, any task that could not be made with why, and Go to the queue. The file counts against the daily quota as a whole, and when one task is wrong none is made.

The prototype cannot choose a file: Download a sample and Create tasks open the note on From a file.

4. Create a scheduled job in three steps, then pause it

For anything that runs on a clock, such as a nightly report.

1. In the sidebar, click Jobs: Jobs.
2. Click Create job: Create a job, at step 1, Define the schedule.
3. Type a Name, pick the Kind (Call a target, or Uptime check), and type the Frequency in unix-cron (0 9 * * 1 is every Monday at 9:00) and the Time zone. The step shows the next 5 runs. Click Continue.
4. Step 2, Configure the execution: the target, HTTP or a queue to add a task to, and the call. Click Continue.
5. Step 3, Configure optional settings: the retries and the attempt deadline. Click Create.
6. The job’s page opens, Job logs, saying “Created the job” and its name once.
7. Click Pause in the job’s toolbar. It shows while the job is enabled; nightly-report in the picture is already paused, so it shows Resume.

Expected: the job reads Paused, and its scheduled times do not run until someone clicks Resume.

Steps 2 and 3, and Pause, are not pictured. See the note on the three steps.

5. Give an app an API key, and store a secret it will use

For a developer connecting an app to the console.

1. In the sidebar, click API keys: API keys.
2. Under Create an API key, type a Key name, such as the app’s name, and an Expires date if the key should end. Click Create key.
3. The key is shown once, with a copy button: put it in the app’s settings now. After that the console shows only its name.
4. In the sidebar, click Secrets: Secrets.
5. Under Add a secret, type a Name, pick the Kind (HMAC signing secret, Basic auth, Bearer token, OAuth client or Google Chat webhook), fill in what that kind takes, and click Add the secret. For Basic auth, a bearer token or an OAuth client, list the https origins it may be sent to.

Expected: the secret is listed by name, never by its value; an HMAC signing secret is made by the console and shown once. A task or job then picks it by name in its Auth, and the app sends its key with each call to the console’s API.

6. Copy a project’s settings with Export and import

For setting up a second project like the first.

1. With the project to copy chosen at the top, click Export and import in the sidebar: Export and import.
2. Click Download. It saves shop-settings.json: the queues, the jobs, the alert settings, the daily quota, and the names of the secrets and service accounts. Never a secret’s value, a key or a token.
3. Choose the other project in the picker at the top, and open its Export and import.
4. Under Settings file, choose the file and click Preview: a dry run that lists what would be made, changed and skipped, and the secrets and service accounts the other project lacks.
5. Add any missing secrets on its Secrets page, then click Apply.

Expected: the changes are made in one go, with one audit line. Nothing is deleted or renamed, and no secret is made.

In the prototype, Preview opens the note on Export and import.

7. Check the free plan’s usage and set alerts

For the owner, keeping the console on the free plan.

1. In the sidebar, click Usage: Usage. The free plan’s four lines (Worker requests, Durable Object requests, D1 rows read and D1 rows written) each have a level, and each project’s tasks and runs today stand against its daily cap.
2. As an admin, click Set the cap on a project’s row to change it: 1 to 1,000,000, 0 for no cap, or back to the default of 5,000.
3. Choose the project at the top, then click Alerts in the sidebar: Alerts.
4. Under Where alerts go, type the email addresses (console users who may read the project) and pick a Google Chat webhook, or follow Add one on the Secrets page. Under When to alert, set the events. Click Save.
5. Click Send a test. Under Quiet hours, set a window and its time zone, and click Save quiet hours.

Expected: alerts reach the addresses and the chat when an event happens, at most one of a kind about a project every 10 minutes. On a queue’s Metrics tab, Create alerting policy opens the same page.

8. Invite a person, and read the audit log

For an admin bringing in a colleague.

1. In the sidebar, under Admin, click People: People.
2. Click Invite. In Invite someone, type the Email of the Google account they will sign in with, and pick the Role: member (the default) or admin.
3. For a member, tick the permissions per project, or pick a preset (viewer, editor or manager) to tick them. Click Send the invitation.
4. A notice says they were invited, and the invitation is listed under Invitations with Resend and Cancel. They accept from the link in their mail, with Google.
5. In the sidebar, click Audit log: Audit log. Each line gives when, who, the project, the action (such as job.create or alerts.update), the target and the detail, newest first. Pick a project under Show to see only its lines.

Expected: the invitation is in the audit log as invitation.create, and its acceptance as invitation.accept.

The Invite form is not pictured.