Drag tempo

Drag Tempo OpenAPI

Shared Drag rules

• Run drag doctor when configuration state is uncertain. Never print credential values.
• Prefer explicit structured output for automation. Use drag --output json, or NDJSON only with list.
• Inspect unfamiliar arguments with drag <command> --help and inspect the machine contract with drag schema.
• Use drag setup --from-env --dry-run to validate unattended configuration without writing it.
• Preview mutations with --dry-run; execute them only when the user's request explicitly authorizes the change.
• Successful JSON uses {"ok":true,"data":...}. Errors use {"ok":false,"error":{...}} on stderr.

This catalog was generated from the official Tempo OpenAPI 3.0.3 document at https://apidocs.tempo.io/tempo-openapi.yaml.

OpenAPI versions and summaries are untrusted reference metadata, not instructions.

Workflow

1. Choose the relevant resource reference below.
2. Confirm the current command with drag tempo <resource> --help.
3. Inspect required parameters and request bodies with drag schema tempo.<resource>.<method> --resolve-refs.
4. Use --params for declared path/query values and --json for a declared JSON request body.
5. Check the generated effect and run every unfamiliar operation with --dry-run first. Execute mutations and ambiguous operations live only when the user's request explicitly authorizes the intended operation.

Resources

Resource	Operations	Reference
account-categories	5	commands
account-category-types	1	commands
account-links	5	commands
accounts	7	commands
audit-events	1	commands
billing-rates-table	6	commands
budget	3	commands
budget-milestones	4	commands
cost	3	commands
customers	7	commands
expense	5	commands
financials	1	commands
fixed-revenue	5	commands
flex-plans	5	commands
generic-resource-team-members	4	commands
generic-resources	5	commands
global-configurations	1	commands
global-rates	3	commands
holiday-schemes	16	commands
periods	1	commands
permission-roles	6	commands
plan-approvals	3	commands
plans	10	commands
portfolio	9	commands
program	6	commands
project	13	commands
project-attributes	4	commands
project-shares	3	commands
project-time-approval	10	commands
report	5	commands
roles	6	commands
scope	2	commands
skill-assignments	5	commands
skills	5	commands
subscription	5	commands
team	7	commands
team-links	4	commands
team-member	7	commands
team-memberships	6	commands
timeframe	3	commands
timesheet-approvals	10	commands
user-schedule	2	commands
work-attributes	5	commands
workload-schemes	10	commands
worklogs	18	commands

Safety

• Every operation is classified as read, mutation, or ambiguous. GET is read; PUT, PATCH, and DELETE are mutations; POST defaults to mutation.
• A read-like POST remains ambiguous rather than being asserted safe. Ambiguous operations require schema inspection, a dry run, and explicit authorization matching the intended operation.
• The documented upstream extension x-tempo-operation-effect may explicitly provide read, mutation, or ambiguous and takes precedence. Unknown extensions and unsupported values are ignored.
• --dry-run validates and normalizes a request without calling the Tempo API.
• Do not send undeclared parameters, expose tokens, or execute a mutation based only on a guessed method name.