This pull request renames the timeout field to duration within the enforceTimeout middleware configuration for OpenAPI (OAS) definitions. This change improves the clarity of the API contract, as the field supports sub-second values (e.g., "100ms"), and duration is a more descriptive name.

Files Changed Analysis

The changes are a consistent rename operation across 5 files within the apidef/oas package, with an equal number of additions and deletions (19).

• apidef/oas/middleware.go: The core change is here. The EnforceTimeout.Timeout struct field is renamed to Duration, and its json and bson serialization tags are updated accordingly. The Fill and ExtractTo methods, which handle mapping to the classic API definition, are also adjusted.
• apidef/oas/schema/*.json: Both the standard and strict JSON schemas for the x-tyk-api-gateway extension are updated, renaming the timeout property to duration.
• apidef/oas/*_test.go: References in linter_test.go and middleware_test.go are updated to use the new Duration field, ensuring continued test coverage.

Architecture & Impact Assessment

• What this PR accomplishes: It enhances API clarity and developer experience by using a more intuitive field name for a value that accepts time duration strings.
• Key technical changes introduced: A Go struct field and its serialization tags were renamed, which in turn modifies the public-facing JSON schema for the x-tyk-api-gateway extension.
• Affected system components: This is a breaking change for users who define APIs via OAS and utilize the enforceTimeout middleware. They will be required to update their API definition files to use the new duration field. The impact is confined to the OAS definition processing layer.

Data Transformation Flow

graph TD
    subgraph "OAS API Definition (User Input)"
        A["x-tyk-api-gateway:<br/>  enforceTimeout:<br/>    duration: 100ms"]
    end

    subgraph "Tyk Gateway (Go Code)"
        B[&quot;struct EnforceTimeout &#123;<br/>  Duration tyktime.ReadableDuration json:&quot;duration&quot;<br/>&#125;&quot;r/>&#125;&quot;]
    end

    subgraph "Tyk Classic API Definition (Internal)"
        C["apidef.HardTimeoutMeta &#123;<br/>  TimeoutDuration: 100ms<br/>&#125;"]
    end

    A --|JSON Unmarshal|--> B
    B --|ExtractTo|--> C

Scope Discovery & Context Expansion

The scope of this change is well-contained within the apidef/oas package. However, the impact is external, as it introduces a breaking change to the x-tyk-api-gateway extension's API contract. This will require updates to user-facing documentation and must be clearly communicated in release notes to avoid disruption for users of this feature.

Powered by Visor from Probelabs

Last updated: 2026-06-10T04:11:01.735Z | Triggered by: pr_updated | Commit: 1aebfa8

💡 TIP: You can chat with Visor using /visor ask <your question>

Architecture Issues (1)

✅ Performance Check Passed

No performance issues found – changes LGTM.

✅ Quality Check Passed

No quality issues found – changes LGTM.

Powered by Visor from Probelabs

Last updated: 2026-06-10T04:10:49.317Z | Triggered by: pr_updated | Commit: 1aebfa8

💡 TIP: You can chat with Visor using /visor ask <your question>

🎯 Recommended Merge Targets

Based on JIRA ticket TT-12339: [BE] Implement sub-second timeout for the Enforced Timeout middleware

Fix Version: Tyk 5.14.0

⚠️ Warning: Expected release branches not found in repository

Required:

• master - No matching release branches found. Fix will be included in future releases.

📋 Workflow

1. Merge this PR to master first

LGTM.

@jay-deshmukh can you please fix the CI and then proceed with merging this PR?

🚨 Jira Linter Failed

Commit: 1aebfa8
Failed at: 2026-06-10 04:09:46 UTC

The Jira linter failed to validate your PR. Please check the error details below:

failed to get Jira issue: failed to fetch Jira issue TT-12339: Issue does not exist or you do not have permission to see it.: request failed. Please analyze the request body for more details. Status code: 404

Next Steps

• Ensure your branch name contains a valid Jira ticket ID (e.g., ABC-123)
• Verify your PR title matches the branch's Jira ticket ID
• Check that the Jira ticket exists and is accessible

This comment will be automatically deleted once the linter passes.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud