Should AzureFunctionsWebHost:hostId be slot-sticky?
I have an Azure Functions app whose name is longer than 32 characters. This app has a production slot and a staging slot. Their default host ids will hence cause collisions, as explained in HostID.
GitHub - Azure/azureml-examples: Official community-driven Azure Machine Learning examples, tested with GitHub Actions.
Official community-driven Azure Machine Learning examples, tested with GitHub Actions. - Azure/azureml-examples
Using Deployment Slots With Azure Web Apps | Documentation and ...
I've enabled GitHub Actions for my Azure App Service Dev Slot, but it fails on the deployment step using the webapps-deploy action. ##[error]Failed to deploy web package to App Service.