You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue occurs when I am trying to publish a single API from test version to higher up in prod env. Even when I try to publish all the artifacts it gives this error. But this is coming even when I have a single api details. The downloading artifacts and everything is success, but when it comes to stage to Run the publisher in the new env it fails.
##[error]Unhandled exception. System.InvalidOperationException: Could not obtain mandatory reference to LoggerResource in property LoggerId of DTO apis/accountsreceivable-v1/diagnostics/local. Property 'LoggerId' is invalid. JSON object does not have a property named 'LoggerId'.
It has extracted the API correctly what is necessary is there in the artifacts.
Expected behavior
It should publish the API in the production env
Actual behavior
It fails with ##[error]Unhandled exception. System.InvalidOperationException: Could not obtain mandatory reference to LoggerResource in property LoggerId of DTO apis/accountsreceivable-v1/diagnostics/local. Property 'LoggerId' is invalid. JSON object does not have a property named 'LoggerId'.
It has extracted the API correctly what is necessary is there in the artifacts.
Reproduction Steps
Just run the extractor only fetch single api.
This is the configuration-extractor.yaml
apis:
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.
Activity
github-actions commentedon Oct 14, 2026