Problem statement
We would like support for a function backend like we have in azure static websites.
We’d like to have included functions with the Rayfin project. Functions need to support both typescript for api calls, and .Net to support the app making xmla endpoint calls using the ADOMD library. .Net is very important when working directly with the XMLA endpoint.
Also would like to see internal rayfin functions supported like having RayFin auto deploy Fabric UDF that is securely connect to the frontend.
In an Azure Static Webapp we can also bring our own azure functions. This enables us to use different languages and more developer support. I’d like to have the same ability with RayFin:
We use managed APIs today and azure static websites and it’s really useful: https://learn.microsoft.com/en-us/azure/static-web-apps/apis-overview#api-options
Proposed solution
Allow for managed functions to be written in typescript or .Net, managed functions would deploy as fabric UDF.
Also allow for azure functions to be supported.
Alternatives considered
No response
Additional context
No response
Problem statement
We would like support for a function backend like we have in azure static websites.
We’d like to have included functions with the Rayfin project. Functions need to support both typescript for api calls, and .Net to support the app making xmla endpoint calls using the ADOMD library. .Net is very important when working directly with the XMLA endpoint.
Also would like to see internal rayfin functions supported like having RayFin auto deploy Fabric UDF that is securely connect to the frontend.
In an Azure Static Webapp we can also bring our own azure functions. This enables us to use different languages and more developer support. I’d like to have the same ability with RayFin:
We use managed APIs today and azure static websites and it’s really useful: https://learn.microsoft.com/en-us/azure/static-web-apps/apis-overview#api-options
Proposed solution
Allow for managed functions to be written in typescript or .Net, managed functions would deploy as fabric UDF.
Also allow for azure functions to be supported.
Alternatives considered
No response
Additional context
No response