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

[Feature]: Azure Functions Support #88

Open
bucanero14 opened this issue Jan 16, 2023 · 3 comments
Open

[Feature]: Azure Functions Support #88

bucanero14 opened this issue Jan 16, 2023 · 3 comments

Comments

@bucanero14
Copy link

bucanero14 commented Jan 16, 2023

Describe the feature you'd like.

Do you have any plans to support Azure Functions? The app I'm currently maintaining relies heavily on it and it would be great to have Console Ninja support this.

@smcenlly
Copy link
Member

Can you please provide a sample project that uses Azure Functions at dev time so we can see how it works?

@bucanero14
Copy link
Author

I found this link to a sample repo a guy created using Azure Functions. If this may help you: https://github.com/Azure-Samples/durablefunctions-apiscraping-nodejs

Also, here's a link to Microsoft's documentation on how to setup the environment and create a simple project (Azure account required): https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-node

@smcenlly
Copy link
Member

Thanks for the details. We found a project (https://github.com/bbachi/azure-func-postgres-ts) that can run locally if we install azure-functions-core-tools for the project.

The Azure Functions support a number of different languages:

  • C#
  • F#
  • Java
  • PowerShell
  • Python
  • JavaScript / TypeScript

We might be able to add limited support for JavaScript / TypeScript only when running Azure functions locally. We definitely wouldn't be able to support the other languages at this point in time.

Having had a play with the Azure functions, they do not seem to work nicely in a fast-feedback environment. For example, by default, you need to run npm start after each code change in order for your changes to take effect. Also, unlike other tooling, the azure function code runs on your compiled files, instead of your source files, which is not the scenario that console ninja currently supports; in contrast, console ninja expects your tooling to run on your source files. There's an open issue for first class hot reload support (from April 2019), which we would need to support console ninja on node workers.

I'll leave this feature request open but given the limited support we could provide (node worker only) and missing support for source changes to be picked up by the azure-functions-core-tools, we are unlikely to support in the near term.

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

2 participants