Closed XiaofeiCao closed 9 months ago
For (3), should we ask service to fix?
LRO not marked as LRO means every SDK fails.
For (3), should we ask service to fix?
LRO not marked as LRO means every SDK fails.
Yeah, I'll ask them for confirmation. CLI team seems to be aware of this issue too: https://github.com/Azure/azure-cli/blob/dev/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L1558
FunctionApp functionApp = appServiceManager.functionApps().define(webappName)
.withRegion(Region.US_EAST)
.withNewResourceGroup(rgName1)
.withManagedEnvironmentId(managedEnvironmentId) // create with managedEnvironmentId
//.withManagedEnvironmentName(managedEnvironmentName) // create with managedEnvironmentName
.withMaxReplicas(10) // with scale setting
.withMinReplicas(3) // with scale setting
.withBuiltInImage(FunctionRuntimeStack.JAVA_17)
.withAppSetting("WEBSITE_RUN_FROM_PACKAGE", FUNCTION_APP_PACKAGE_URL)
.create();
functionApp.update()
.withMaxReplicas(15) // with scale setting
.withMinReplicas(5) // with scale setting
.apply();
2.34.0 released.
docs: https://learn.microsoft.com/en-us/azure/azure-functions/functions-container-apps-hosting
It's a new hosting plan compared to previous App Service Plans: All hosting plans
Some major implementation differences(found in azure-cli, may not be exhaustive): For managed container app environment based(Centauri) Function Apps