DPtoCP: GraphQL API CRs Applied but Not Visible in Control Plane

[terance-edmonds]

Description

Description

In the DP to CP flow, when applying GraphQL API CRs, the CRs are successfully applied, but the API cannot be invoked and, the API is not visible in the Control Plane.

Expected Behavior

The API should be visible in the Control Plane once the CRs are applied successfully.

Actual Behavior

The API does not appear in the Control Plane UI

graphql-sample-crs.zip

Steps to Reproduce

1. Apply the GraphQL API CRs.
2. Verify that the API is deployed and accessible via cURL or Postman.
3. Check the Control Plane UI – the API is not listed.

Affected Component

Adapter

Version

1.3.0

Environment Details (with versions)

• WSO2 APK Version: 1.3.0
• Kubernetes Version: 1.30.7

Relevant Log Output

2025-03-10 08:45:20 INFO [publisher_rest_api_utils.go:247] - [utils.ImportAPI] [-] For the API import we received response status: 400  Status code: 400. API zip name admin-Starwars API-1.0.zip, response body: {"code":902008,"message":"API policy is not allowed in the applied flow","description":"%s policy is not allowed in response flow","moreInfo":"","error":[]} []
[GIN] 2025/03/10 - 08:45:20 | 200 |   63.741782ms |      10.42.0.26 | POST     "/apis"

Related Issues

No response

Suggested Labels

No response