Use of shared flow

Google Cloud Apigee Knowledge Hub
1

Hi all,

This article I am preparing as per the scenarios I came across during my work experience.

Shared flow is new for some developers. So, I noticed there are many developers creating shared flows with n number of policies with conditions specific to proxies. And that’s not the goal of shared flow.

Shared flow is aimed to distinguish reusable codes and bundle then for the future shared use. There is a scope of adding conditions in the shared flow. But if you will add everytime a new policy in the shared flow with condition by proxy name then the purpose of shared flow is falsified. For a very few and rare cases some policies can be skipped or added, but the addition of too many policies should not be accepted. And also this increases the processing time as it has to validate n number of conditions.

2

Hi, do you have docummentation about how create a shared flow because right now i’m developing so many proxy, each of them with different policies, but i need shared flow for basic policies like OAUTH2 Autentication and validation token.

3

I don’t have any document.

You can refer: https://docs.apigee.com/api-platform/fundamentals/shared-flows

You should put the reusable policies in the shared flow.

Don’t add any proxy specific policies in the shared flow.