I have to make a lot of raw requests. Due to that, we aren't getting full payload objects as well as typings. I tried to leave a bunch of TODO comments to clarify why it's currently like that, but feel free to ask for more clarification.
Eventually we'll have to change the SDK, and at that time, we'll have to update a lot of our appservice package (because SiteClient relies on a particular format for the payload). For now, I'm getting around that by using the old SDK to do things like get calls. I chose to do this for now because a preview feature shouldn't cause us to fundamentally change the core of our extension (since a lot of things rely on the SiteClient)
Because of ASP stack/OS compatibilities, the Functions team requested that we ask the ASP immediately after the name step.
---BEGIN COPILOT---
This pull request introduces changes to enable the creation of Flex Consumption Function Apps, a preview feature for Azure Functions. The changes include adding a new setting for enabling Flex Consumption, modifying the function app creation process to support Flex Consumption, and adding new properties for Flex Function Apps.
New Setting:
package.json: Added a new setting azureFunctions.enableFlexConsumption to enable the creation of Flex Consumption Function Apps.
package.nls.json: Added a description for the new setting azureFunctions.enableFlexConsumption.
Function App Creation:
src/commands/createFunctionApp/FunctionAppCreateStep.ts: Modified the function app creation process to support Flex Consumption. This includes changes to the FunctionAppCreateStep class to handle the creation of Flex Function Apps and the addition of new methods for creating Flex Function Apps. [1][2][3][4][5][6][7][8]
Couple of clarifications:
I have to make a lot of raw requests. Due to that, we aren't getting full payload objects as well as typings. I tried to leave a bunch of TODO comments to clarify why it's currently like that, but feel free to ask for more clarification.
Eventually we'll have to change the SDK, and at that time, we'll have to update a lot of our appservice package (because SiteClient relies on a particular format for the payload). For now, I'm getting around that by using the old SDK to do things like get calls. I chose to do this for now because a preview feature shouldn't cause us to fundamentally change the core of our extension (since a lot of things rely on the SiteClient)
Because of ASP stack/OS compatibilities, the Functions team requested that we ask the ASP immediately after the name step.
---BEGIN COPILOT--- This pull request introduces changes to enable the creation of Flex Consumption Function Apps, a preview feature for Azure Functions. The changes include adding a new setting for enabling Flex Consumption, modifying the function app creation process to support Flex Consumption, and adding new properties for Flex Function Apps.
New Setting:
package.json: Added a new settingazureFunctions.enableFlexConsumptionto enable the creation of Flex Consumption Function Apps.package.nls.json: Added a description for the new settingazureFunctions.enableFlexConsumption.Function App Creation:
src/commands/createFunctionApp/FunctionAppCreateStep.ts: Modified the function app creation process to support Flex Consumption. This includes changes to theFunctionAppCreateStepclass to handle the creation of Flex Function Apps and the addition of new methods for creating Flex Function Apps. [1] [2] [3] [4] [5] [6] [7] [8]src/commands/createFunctionApp/FunctionAppHostingPlanStep.ts: Added logic to handle Flex Consumption in theFunctionAppHostingPlanStepclass. [1] [2]src/commands/createFunctionApp/stacks/FunctionAppStackStep.ts: Updated theFunctionAppStackStepclass to handle Flex Consumption. [1] [2] [3] [4] [5]Flex Function App Properties:
src/commands/createFunctionApp/FunctionAppCreateStep.ts: Added new properties for Flex Function Apps.src/commands/createFunctionApp/IFunctionAppWizardContext.ts: Added a new propertynewSiteStackFlexto theIFunctionAppWizardContextinterface to support Flex Consumption.