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

Value of policy for get operation is getting replaced by ASCII character after running extractor file #590

Open
Anand2042 opened this issue Jul 18, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Anand2042
Copy link

Anand2042 commented Jul 18, 2024

Release version

APIOPS toolkit for Azure APIM

Describe the bug

In the get operation, user is applying one rewrite policy and the value of policy get changed when extracted the file while running the extraction file in pipeline and then user publish the pipeline but it start showing error while running the operation.

Expected behavior

In the get operation, when user is running extraction file then the value of policy should be as it is required and set in portal.

Actual behavior

But when user is running the extraction file then some character get replaced with ASCIII character in the value of policy and then manually modifying the changes in pipeline to publish the pipeline successfully.

Reproduction Steps

User using the rewrite policy in get and then running the extractor file. After extraction we can notice in file of policy created in artifacts that some of the value of policy is getting changed with ASCII character.

Copy link

  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

Can you please check if there is an existing issue that addresses the same issue? Please search both open and closed issues.

@Anand2042
Copy link
Author

yes, searched the open and closed issues and reviewing it whether our issue is mentioned there or not.

@waelkdouh waelkdouh added the bug Something isn't working label Jul 29, 2024
@guythetechie
Copy link
Contributor

Can you post samples? What does your original policy look like, and what does it look like after extraction?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants