Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Bug] Selective API operation extraction filter does not filter paths in specification.yaml

Abierto
#294 0 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
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, cli

Línea de trabajo

Start with the apiops extract entry point and the filter configuration at configuration/extractor.config.yaml. Compare how the operations allow-list is applied to artifacts/apis/api1/operations/ versus artifacts/apis/api1/specification.yaml. Done means the specification contains only the selected operation paths while excluded operation artifacts remain absent.

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

Descripción

type:bug
Command that triggered the bug

apiops extract

Expected behavior

When an API is configured with an operations allow-list, the generated specification.yaml should contain only those selected operations.

For example:

apis:
  - api1:
      operations:
        - create-resources

If the api1 API contains create-resources and test, only create-resources should appear in: specification.yaml



### Actual behavior

The extractor correctly filters the individual operation artifacts. Only the selected operation is generated under:

artifacts/apis/api1/operations/

However, artifacts/apis/api1/specification.yaml still contains the other operations path.

As a result, publishing the extracted artifacts can create the excluded operation in the target APIM instance, even though it was not listed in the extractor filter.

This is the same behavior described in for the older apiops [Azure/apiops#854](https://github.com/Azure/apiops/issues/854).

### apiops CLI version

1.0.3

### Environment details

APIOps CLI package: @azure-tools/apiops-cli
APIOps CLI version: 1.0.3
Node.js: 22.x or later
Package installation: npm ci
Command: apiops extract
Filter option: --filter configuration/extractor.config.yaml

### CI/CD environment

Azure DevOps

### Is this bug blocking you?

Yes
Lenguaje dominante
TypeScript
Estrellas
29
Forks
10
Merge medio
1 d 13 h
PR fusionados (30 d)
23

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-cli

Todos los issues de Azure/apiops-cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.