are extensions supported in Apigee x and Apigee hybrid

[surbhijain_30]

are extensions supported in Apigee x and Apigee hybrid

[dchiesa1]

For X and hybrid, We've moved away from the Apigee Extensions thing that is supported in Apigee Edge. We have some better options now.

The way I think of it, there are three ways to "extend" Apigee X and hybrid

• extension policies. This allows you to write JavaScript, Java code, Python (Jython) code, to perform custom tasks within the context of an API request/response flow. As an example of this "custom task" idea, here is a custom Java policy that performs ECDSA signature creation and validation within Apigee. JavaScript is probably the most common of these 3 language options, because it's so easy to write.

• ExternalCallout - this is a nifty capability, newly added for Apigee X and hybrid, that allows you write your own service exposed as gRPC, and connect to it from your Apigee X or hybrid message processor. The service runs outside of the MP, and because of that, allows greater flexibility in the implementation. You can use bonafide Java, Golang, Python , C#. This does require some programming on your part.

• Apigee Integration and Connectors . he current list of available connectors is short, and provided here. Expect that list to grow quickly over time.

[anilmoregfs]

@dchiesa1 What is the recommended approach out of the above three options (especially for cloud function, cloud run, and serverless extensions)? 

[dknezic]

You really need to be more specific on what your use case is.

If you were using an Apigee extension and for a Google Cloud service, you could probably use a combination of out of the box capabilities by interacting with that service' API directly - ie Service Callout policy and leverage Google Authentication built into Apigee API Proxies.

https://cloud.google.com/apigee/docs/api-platform/security/google-auth/overview