APIOPs extractor Pipeline not extracting operations of gRPC API in the Pull request.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Use the reproduction steps against release v6.0.1.4, starting with the APIOPs extractor pipeline and its “Create artifacts pull request” step. Compare the generated customer-grpc apiInformation.json with the deployed gRPC API's operations; the work is done when the pull request includes all operations from the customer profile service proto.
Written by the indexing model from the issue text.
Description
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
- Create a gRPC API in APIM with customer profile service proto file.
- gRPC API should be created with multiple operations.
- Execute the run extractor pipeline of APIOPS.
- The "Create artifacts pull request" - "Create pull request" step of the extractor pipeline would create a PR.
- The PR will not have operations data of the gRPC API.
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·