search

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
308 stars 180 forks source link

[BUG] Error in element 'rewrite-uri when publish #605

Open PeiyuKuo opened 1 month ago

PeiyuKuo commented 1 month ago

Release version

Latest

Describe the bug

"rewrite-uri" policy will be created automatically when we use apiops to import logic app to azure APIM ,and it used the correct HTML code to show "&" not "&" when extract. But the publisher omits policy to the wrong operation

Expected behavior

Export by "Name" rather than "Display name"

Actual behavior

Import fails with a cryptic error: crit: Microsoft.Extensions.Hosting.Internal.Host[10] The HostOptions.BackgroundServiceExceptionBehavior is configured to StopHost. A BackgroundService has thrown an unhandled exception, and the IHost instance is stopping. To avoid this behavior, configure this to Ignore; however the BackgroundService will not be restarted.

System.Net.Http.HttpRequestException: HTTP request to URI rawxml failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"rewrite-uri","message":"Error in element 'rewrite-uri' on line 5, column 4: Cannot find a property 'XXXX-XXXXX_When_a_HTTP_request_is_received-invoke_668b900f943bcd252dc199a3'"}]}}'. raw log.txt

Reproduction Steps

  1. Run extractor
  2. Run the Publisher
github-actions[bot] commented 1 month ago 
  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.
guythetechie commented 1 month ago

Can you share the policy file under /artifacts/apis/wyhq-nileplus-d-nifiserverlog/operations/When_a_HTTP_request_is_received-invoke/policy.xml?

PeiyuKuo commented 1 month ago

Hi

File as attachment, thanks.

PeiyuKuo commented 1 month ago

hi

any updates?

waelkdouh commented 1 month ago

This is an open source project so please be patient. No need to check with us as we will respond when we have a chance to take a look at your issue.

guythetechie commented 1 month ago

@PeiyuKuo - I don't see anything attached. Don't know if Github uploads attachments to the issue when you respond by email. Can you try uploading your file?

PeiyuKuo commented 1 month ago

i've uploaded zip file, thanks. policy.zip