Skip to content

API-level apiPolicies dropped by apictl init --definition #5088

Description

@dinuka10

Description

When using apictl init --definition, any apiPolicies defined under the data section of the definition file are silently dropped and do not appear in the generated api.yaml.

Steps to Reproduce

Steps to Reproduce

  1. Create an OAS file (petstore.yaml) and a definition file (api-definition-issue1.yaml) with apiPolicies defined under the data section and operationPolicies defined within the API operations.

  2. Run the following command to initialize the API project:

apictl init PetStoreICA-Issue1 \
  --oas petstore.yaml \
  --definition api-definition-issue1.yaml \
  -f
  1. Inspect the generated api.yaml file.

    • apiPolicies are absent (silently dropped).
    • operationPolicies defined within operations are present and preserved correctly.

Version

4.5.0

Environment Details (with versions)

No response

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions