-
Notifications
You must be signed in to change notification settings - Fork 192
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] Error in element 'rewrite-uri when publish #605
Comments
|
Can you share the policy file under |
Hi
File as attachment, thanks.
|
hi any updates? |
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. |
@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? |
i've uploaded zip file, thanks. |
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
The text was updated successfully, but these errors were encountered: