Repository navigation
Billing: Confidential Workflow add execution_duration_ms - #469
Conversation
…owResponse Enclave-measured wall-clock duration of the WASM execution in milliseconds, so the workflow node can emit a cre:workflow:compute usage MeterRecord for confidential executions (CRE-6780). Optional: presence distinguishes an unavailable measurement from a measured zero, and older enclaves leave it unset. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
|
The latest Buf updates on your PR. Results from workflow Regenerate Protobuf Files / buf (pull_request).
|
DylanTinianov
changed the title
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The additive optional field is backward-compatible and the embedded definition matches its source.
Review effort: Balanced
Findings: None
What changed in this PR
Adds an optional confidential workflow execution duration for downstream compute metering.
Changes:
- Adds
execution_duration_mswith presence semantics. - Synchronizes the embedded protobuf definition.
| File | Description |
|---|---|
cre/capabilities/compute/confidentialworkflow/v1alpha/client.proto |
Extends the response schema. |
cre/go/installer/pkg/embedded_gen.go |
Updates the embedded schema copy. |
Files not reviewed (1)
- cre/go/installer/pkg/embedded_gen.go: Generated file
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Adds
optional int64 execution_duration_ms = 3toConfidentialWorkflowResponse(CRE-6780).The enclave measures the wall-clock duration of the WASM execution and returns it so the workflow node can emit a
cre:workflow:computeusage MeterRecord for confidential executions, the same resource type and unit as ordinary compute.optionalso presence distinguishes an unavailable measurement from a measured zero; older enclaves leave it unset and the node emits nothing.