Skip to content

Wso2 apim does not return an error message when creating an api with wrong policy name using apictl #809

@selakap

Description

@selakap

Description

When deploying an API into the APIM-4.1.0 via the API Controller (apictl), we define the integration policies that are required for their APIs, in the api.xml file as shown below. But the defined policy is not there under the common Policies or API-specific policies in the wso2 apim setup.

id: ""
target: /*
verb: POST
authType: None
throttlingPolicy: Unlimited
scopes: []
usedProductIds: []
operationPolicies:
request:
-
policyName: globalAPKlogsequence
policyVersion: v1
parameters:
message_type: invoice
direction: outgoing request
key_name: invoiceid
key_xpath: $body/oag:Invoice/oag:Header/oag:DocumentIds/oag:DocumentId/oag:Id
key_namespace: xmlns:oag="http://www.openapplications.org/oagis"

Ideally, there should be an error message and fail the API creation. Instead of that wso2 apim will create the API without the policy.

Steps to Reproduce

Try to create an API in APIM-4.1.0 using apictl tool with an invalid (wrong) policy name as mentioned above

Affected Component

APIM

Version

4.1.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions