wso2 / wso2/api-platform

[Bug]: Deleting an LlmProviderTemplate that an LlmProvider references succeeds, leaving the provider

Open
#3,210 1 comment 0 reactions 2 assignees View on GitHub

@thivindu is already working on this.

Since Aug 14, 2026.

Aspect/API Severity/Major 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

Gateway

Please select the aspect the issue is related to

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

Description

DELETE /llm-provider-templates/{id} succeeds even when a deployed LlmProvider still references the template. The provider is left holding a reference and can no longer be updated or redeployed and any subsequent PUT fails with failed to retrieve template.

Steps to Reproduce

All requests against http://localhost:9090/api/management/v1, basic auth.

  1. POST /llm-provider-templates - create a template named demo-ref-template.

  2. POST /llm-providers - create a provider named demo-ref-provider referencing the above template

  3. DELETE /llm-provider-templates/demo-ref-template

  • Actual: 200 OK, "LLM provider template deleted successfully"

  • Expected: 409 Conflict

  1. GET /llm-provider-templates/demo-ref-template → 404, template is gone

  2. GET /llm-providers/demo-ref-provider → 200, still present, still referencing the deleted template.

  3. PUT /llm-providers/demo-ref-provider with an unchanged body → gives error as it references a template that doesn't exist

Severity Level of the Issue

Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)

Environment Details (with versions)

No response

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.