Duration

What it does

Converts between a Go duration string ("5m", "1h30m") and an integer number of seconds. Compile infers which side is the string from the schemas. Parsing uses time.ParseDuration.

When to use it

A timeout, interval, or TTL stored as a duration string on one API version and as integer seconds on another. This is not Kubernetes resource.Quantity — "5m" here is five minutes, not five millicores. Use Quantity for resource amounts.

Integer seconds → canonical duration string is lossy

Parsing a whole-second duration string into seconds is exact. A duration with a sub-second remainder (1500ms) is a runtime conversion error, not silent truncation. Writing seconds back out uses Go's canonical Duration.String() spelling ("5m0s"), which is not always the original string ("5m"). That direction requires acknowledgeLossy: true.

Example

The hub's timeout duration string is stored as seconds on the v1 spoke:

Hub schema (v3)Spoke schema (v1)

spec:
  properties:
    timeout:
      type: string

spec:
  properties:
    timeoutSeconds:
      type: integer

Rule

- strategy: Duration
  duration:
    hubPath: spec.timeout
    spokePath: spec.timeoutSeconds
  acknowledgeLossy: true
  reason: >-
    integer seconds re-format as Go's canonical duration string (5m0s),
    which may differ from an equivalent spelling such as 5m.

Objects

Hub (v3)Spoke (v1)

spec:
  timeout: "5m"

spec:
  timeoutSeconds: 300

Converting 300 seconds back to the hub yields "5m0s", not "5m". That is the acknowledged-lossy direction.