Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APIOPs extractor Pipeline not extracting operations of gRPC API in the Pull request. #718

Open
himaubgb022491 opened this issue Dec 19, 2024 · 2 comments

Comments

@himaubgb022491
Copy link

Release version

v6.0.1.4

Describe the bug

APIOPs extractor Pipeline is not extracting operations of gRPC API in the Pull request.. Followed below steps:
1)Created gRPC API in APIM with customer profile service proto file .
2) gRPC API is deployed with multiple operations.
3) While using APIOPs extractor Pipeline, it is not extracting operations of gRPC API in the Pull request.
In the PR, apis folder with gRPC api "customer-grpc" is extracted with only apiInformation.json but operations are not found.
Attached document with screenshots.

Expected behavior

APIOPs extractor Pipeline should extract all operations of gRPC API in the Pull request.

Actual behavior

APIOPs extractor Pipeline is not extracting operations of gRPC API in the Pull request.

Reproduction Steps

  1. Create a gRPC API in APIM with customer profile service proto file.
  2. gRPC API should be created with multiple operations.
  3. Execute the run extractor pipeline of APIOPS.
  4. The "Create artifacts pull request" - "Create pull request" step of the extractor pipeline would create a PR.
  5. The PR will not have operations data of the gRPC API.
Copy link

  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.

@himaubgb022491
Copy link
Author

Attached document with snippets of PR created by extractor pipeline which is not extracting operations of gRPC API.
ImageAPIOPS_Extractor_Pipeline_Operartions_gRPC_API_Issue.docx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant