[Question] Selective extractor: API specification file contains all operations despite operations filter in configuration

[sonalk-optimus]

Release version

v7.0.2

Question Details

When using the v7 nested operations: configuration to selectively extract a single operation from an API, the extracted specification.yaml still contains all operations of the API, including the ones that were filtered out.

Is this the intended behavior ?

Expected behavior

Given the following configuration.selective-extractor.yaml:
`apis:

• test:
  operations:
  - getoperator
  backends: []
  diagnostics: []
  gateways: []
  groups: []
  loggers: []
  namedValues: []
  policyFragments: []
  products: []
  subscriptions: []
  tags: []
  versionSets: []
  workspaces: []`

The extracted apis/test/specification.yaml should contain only the /getoperator path, since getoperator is the only operation listed under apis.test.operations

This would ensure that when the publisher promotes these artifacts to a target APIM instance, only the selected operation is created in the target API

Actual behavior

The extractor:

• Writes the full API specification at apis/test/specification.yaml, which contains both /getoperator and /postoperator paths

Reproduction Steps

1. In APIM, create an API called test with two operations: getoperator (GET) and postoperator (POST).

2. Create this configuration.selective-extractor.yaml:

`apis:

• test:
  operations:
  - getoperator
  backends: []
  diagnostics: []
  gateways: []
  groups: []
  loggers: []
  namedValues: []
  policyFragments: []
  products: []
  subscriptions: []
  tags: []
  versionSets: []
  workspaces: []`

3. Run the v7.0.2 extractor pointing CONFIGURATION_YAML_PATH at that file

4. If you then run the publisher against a target APIM, both operations get created.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[sonalk-optimus]

Hi @guythetechie , Could you please respond to this

[guythetechie]

@sonalk-optimus - we unfortunately don't support filtering operations in API specifications. The full specification is always extracted. The only operation-level filters we support are operation policies.

To achieve what you're after, you'll need a manual step between extracting and publishing: run extractor, edit specification file to remove undesired operations, then publish. Our tool doesn't do this.