guythetechie
guythetechie
The publisher needs to know where your artifacts are located. It gets that value from the configuration value ``API_MANAGEMENT_SERVICE_OUTPUT_FOLDER_PATH``. By default, our starter pipelines set it to ``$(Build.SourcesDirectory)/artifacts`` [here](https://github.com/Azure/apiops/blob/66cd3921223234a540060f931b6f8159540863af/tools/azdo_pipelines/run-publisher-with-env.yaml#L143C7-L143C48), [here](https://github.com/Azure/apiops/blob/66cd3921223234a540060f931b6f8159540863af/tools/azdo_pipelines/run-publisher.yaml#L62),...
Can you try again with our latest v6 release? There was a [related issue](https://github.com/Azure/apiops/issues/513) that was addressed in the release.
@martin2176 - looking at the code, I don't see a filter for global policy. Can you point to the documentation where it says you can filter out global policy? As...
Can you post your publisher logs?
@username-anonymous - see [our Wiki](https://github.com/Azure/apiops/wiki/APIM-resources#application-insights-loggers) for handling application insights loggers.
@felipementel - did someone modify the `apiInformation.json` file, or is it exactly the one that was generated by the extractor?
@felipementel - looks like the error is happening with a PUT, not a GET. Can you [enable trace logging](https://github.com/Azure/apiops/wiki/Logging) to get more details? It should show you the failing call...
@JamesProant - version 6 changed the way products are associated with APIs. Search for **Subfolder structure** in the [release notes](https://github.com/Azure/apiops/releases/tag/v6.0.0-rc1).
@JamesProant - sorry for the delayed response. Between personal and professional matters, I've had no time for ApiOps. Can you confirm that the APIs aren't filtered in the extractor configuration?...
@JamesProant - this should be fixed in our next release, v7. We have an alpha branch [here](https://github.com/Azure/apiops/tree/v7), if you'd like to clone it and test it. Note that this branch...