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

Creating a plan on a v2 API leads to null values in the description #9153

Closed
exalate-issue-sync bot opened this issue Jul 26, 2023 · 0 comments
Closed

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Jul 26, 2023

Please check this recording: [https://www.loom.com/share/466835b4267e45a88b3d73e586305af8?sid=8713a407-2281-4d16-97af-0fe1a4a79249](https://www.loom.com/share/466835b4267e45a88b3d73e586305af8?sid=8713a407-2281-4d16-97af-0fe1a4a79249)([https://www.loom.com/share/466835b4267e45a88b3d73e586305af8?sid=8713a407-2281-4d16-97af-0fe1a4a79249|https://www.loom.com/share/466835b4267e45a88b3d73e586305af8?sid=8713a407-2281-4d16-97af-0fe1a4a79249])

When creating a plan on a v2 API and adding Rate Limiting and Resource Filtering (haven’t tested with Quota) the description of the two policies is set to the string “null”, same for the “name” and the “condition”.

Please note that in a previous test the flow name was also set to null and the same happened with the flow’s Condition but couldn’t replicate in my video.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants