Reputation: 253
I´m preparing a release to deploy a web app to a Azure App Service and seems that this task is not available as part of an agentless job. Thinking a bit about it, I wonder why. I mean: In my understanding, deploy to Azure is essentially take the artifact (assuming that is already stored in Azure devops) and deploy in the resource provided in the service connection through the actions performed by the Deployment task.
I would say that this process does not (necessarily) requires an agent out of the Azure Devops environment to be done (at the end, we are moving things between PaaS) but seems that we are enforced to use it.
Is my thought correct or I'm missunderstanding anything?
Any way to perform this kind of deployment without agents? (my Azure App Service has a private endpoint, so only self-hosted agents are able to reach it and I would like to avoid create them)
Upvotes: 2
Views: 1406
Reputation: 59001
Any Azure DevOps Pipeline needs an Agent to run it (the workload must run somewhere, right?). If you use private endpoints and you want to PUSH your deployment to Azure App Services, you will have to create a self-hosted Agent that is connected to the App Service VNET. There is no way around it.
However, Azure App Service enables continuous deployment from Azure Repos repositories by pulling the sources (See Continuous deployment to Azure App Service. This will probably also work with private endpoints (not tested it).
Upvotes: 2