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

Abierto
#854 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
azure, csharp
Área
api

Línea de trabajo

Empieza con configuration.selective-extractor.yaml y la ruta del extractor que escribe apis/test/specification.yaml, reproduciendo el caso de v7.0.2 con getoperator y postoperator. Compara la specification generada con la configuración y, después, ejecuta el publisher contra una APIM de destino; se considera terminado cuando solo está presente /getoperator y está promoted.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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: []`

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

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

Lenguaje dominante
C#
Estrellas
448
Forks
247
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/apiops

Todos los issues de Azure/apiops

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.