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

[gateway] Filter disabled flows and flows steps #7794

Closed
Okhelifi opened this issue Jun 2, 2022 · 2 comments
Closed

[gateway] Filter disabled flows and flows steps #7794

Okhelifi opened this issue Jun 2, 2022 · 2 comments

Comments

@Okhelifi
Copy link
Member

Okhelifi commented Jun 2, 2022

Description

In the api definition API class when we load the dependencies we don't check if the flow steps are disabled or not. Or should consider it and filter it.

Here is an example:
Screenshot 2022-06-02 at 15 39 08

I don't have the java script policy. However, I disabled it so I should not have an exception saying Policy ... can not be found in policy registry ( in the backend logs ) when I deploy it and try to call it using postman or even the debug mode in the next versions.

Same for the Flows if a flow is disabled I should not consider it.

@Okhelifi
Copy link
Member Author

Okhelifi commented Jun 2, 2022

Fixed on 3.10.x

@mouligno mouligno added this to the APIM - 3.10.x milestone Jun 7, 2022
@mouligno mouligno added the p3 label Jun 7, 2022
@RubenMMSantos
Copy link

Issue verified and confirmed as fixed.
Policies and flows that are disabled are now successfully ignored and calls are still executed successfully.
Verified on envir 3.10

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

3 participants