Gets logs for functions running in a Kubernetes cluster. For more information, see Creating containerized function apps. For Java functions, you must manually create the Dockerfile. When you use either -docker or -dockerfile options, Core Tools automatically create the Dockerfile for C#, JavaScript, Python, and PowerShell functions. Supported values are: net6.0 (default), net7.0, net8.0, and net48 (.NET Framework 4.8). Valid only with -worker-runtime dotnet-isolated. Sets the target framework for the function app project. When not set, you're prompted to choose your runtime during initialization. To generate a language-agnostic project with just the project files, use custom. Supported values are: csharp, dotnet, dotnet-isolated, javascript, node (JavaScript), powershell, python, and typescript. Sets the language runtime for the project. For more information, see the Python developer guide and the Node.js developer guide, respectively.Ĭontrols whether a git repository is created. Supported options are V1 and V2 for Python and V3 and V4 for Node.js. Sets the desired programming model for a target language when more than one model is available. Currently, only the PowerShell worker runtime supports this functionality. You can also use -worker-runtime javascript or -worker-runtime typescript. Currently supported when -worker-runtime set to node. Other files in the project folder aren't affected. This setting overwrites existing files with the same name. Initialize the project even when there are existing files in the project. Use this option when you plan to deploy a containerized function app and the project already exists. Prompts for the worker-runtime if not specified or set in. Use this option when you plan to deploy a containerized function app.Īdds a Dockerfile to an existing project. Valid only with -worker-runtime dotnet.Ĭreates a Dockerfile for a container using a base image that is based on the chosen -worker-runtime. NET functions as C# script, which is the version 1.x behavior. Otherwise, the current folder is used.įunc init supports the following options, which don't support version 1.x unless otherwise noted: OptionĬreates. When you supply, the project is created in a new folder with this name. func initĬreates a new Functions project in a specific language. Command contextĬommands used to create and run functions on your local computer.Ĭommands for working with Azure resources, including publishing.ĭeploy containerized function app to Azure Container Apps.Ĭommands for working with Durable Functions.Ĭommands for installing and managing extensions.Ĭommands for working with Kubernetes and Azure Functions.Ĭommands for managing environment settings for the local Functions host.Ĭommands for listing available function templates.īefore using the commands in this article, you must install the Core Tools. To learn more about using Core Tools, see Work with Azure Functions Core Tools.Ĭore Tools commands are organized into the following contexts, each providing a unique set of actions. This article provides reference documentation for the Azure Functions Core Tools, which lets you develop, manage, and deploy Azure Functions projects from your local computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |