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

[BUG] - configuration.extractor.yaml is not working as expected, No APIs in the published artifacts. #498

Closed
ParthVyas2912 opened this issue Mar 7, 2024 · 7 comments

Comments

@ParthVyas2912
Copy link

ParthVyas2912 commented Mar 7, 2024

Release version

v5.1.1

Describe the bug

I set pipeline properly. Extractor is working as expected when I select "extract - all" from the desired apim instance it works fine.

But when I pass on value using "configuration.extractor.yaml" file, the value I specified for APIs are not being honored.
Here are the scenarios I tried, with different values for "configuration.extractor.yaml":

apiNames: ['Mock API']

apiNames:

  • Mock API

apiNames:

  • Mock API

backendNames:
diagnosticNames:
loggerNames:
namedValueNames:
productNames:
subscriptionNames:
tagNames:
policyFragmentNames:

for all 3 inputs, I had the same result, where it wasn't extracting the "APIs" results in the artifacts.

image

Expected behavior

I expect that only the apis I added in the "configuration.extractor.yaml" file to be present in the artifacts being published.

Actual behavior

I can't see any APIs being exported

image

Reproduction Steps

Just select one or two APIs in the configuration.extractor.yaml file

Copy link

github-actions bot commented Mar 7, 2024

  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.

@waelkdouh
Copy link
Contributor

Did you follow the instructions in the wiki section on the repository?

@waelkdouh
Copy link
Contributor

Also please check closed issues that have addressed this question in the past.

@ParthVyas2912
Copy link
Author

ParthVyas2912 commented Mar 7, 2024

I followed the steps on the Wiki,

Also, when I select "extract-all" option in the extractor pipeline, the pipeline works as expected (All apis are extracted in the artifact folder). When I select "configuration.extractor.yaml" file, the pipeline works. But API is not published as part of extracted artifacts.

Also, I checked some issues by other folks, and tried to see solution, but I don't see anything that I haven't tried.

Plus, I have one more small issue. Not sure if it is relevant or not. When I use "artifacts" as name for the "Folder where you want to extract the artifacts", the pipeline runs successfully, but PR doesnt get created. If I use any other name for the folder, the PR gets created.

Also thanks a lot for prompt response.

@ParthVyas2912
Copy link
Author

Attached is the extractor pipeline and config files.

extractor - pipeline and config.zip

@guythetechie
Copy link
Contributor

@ParthVyas2912 - "Mock API" is your API display name, not your API name. The configuration file expects an API name, and APIM doesn't support API names with spaces.

image

@ParthVyas2912
Copy link
Author

Ohh, I think I missed it. Thanks for correcting, looks like it is working on my end now.

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

3 participants