wso2 / wso2/api-platform

[Bug]: Successful Deployment of LLM Provider with invalid Policy

Open
#1,547 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1.0.0 Area/Gateway Area/Management Aspect/API Severity/Blocker Type/Bug
Dominant language
Go
Stars
71
Forks
111
Avg merge
1d 14h
Merged PRs (30d)
110

Description

Please select the area the issue is related to

Area/Management (Management API or Management Portal UI), Area/Gateway (Routing, API deployment in gateway etc.)

Please select the aspect the issue is related to

Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)

Description

Response from GW

{
    "id": "wso2-openai-provider",
    "message": "LLM provider updated successfully",
    "status": "success",
    "updatedAt": "2026-03-29T10:21:50.361910356Z"
}
Steps to Reproduce
apiVersion: gateway.api-platform.wso2.com/v1alpha1
kind: LlmProvider
metadata:
  name: wso2-openai-provider
spec:
  displayName: WSO2 OpenAI Provider
  version: v1.0
  template: openai
  vhost: api.openai.local
  upstream:
    url: "https://api.openai.com/v1"
    // auth:
    //   type: api-key
    //   header: Authorization
    //   value: "Bearer $secret{openai-secret}"
  policies:
    - name: set-headerssss
      version: v1
      paths:
        - path: /chat/completions
          methods: [POST]
          params:
            request:
              headers:
                - name: Authorization
                  value: "Bearer $secret{openai-secret}"
Severity Level of the Issue

Severity/Blocker (Core functionality is broken and consumer is blocked. Need immediate attention)

Environment Details (with versions)

1.0.0-rc

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Apply the provided LlmProvider YAML against the 1.0.0-rc environment and compare the gateway response with the invalid policy in the manifest. Trace the deployment path for policy validation. Done means an invalid policy is rejected with an actionable error instead of returning successful deployment, while valid providers continue to deploy.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.