{"action":"opened","issue":{"url":"https://api.github.com/repos/aspnet/AzureIntegration/issues/163","repository_url":"https://api.github.com/repos/aspnet/AzureIntegration","labels_url":"https://api.github.com/repos/aspnet/AzureIntegration/issues/163/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/AzureIntegration/issues/163/comments","events_url":"https://api.github.com/repos/aspnet/AzureIntegration/issues/163/events","html_url":"https://github.com/aspnet/AzureIntegration/issues/163","id":306481254,"number":163,"title":"Site Extension Experience is not good when used with Slots","user":{"login":"graemechristie","id":1361894,"avatar_url":"https://avatars3.githubusercontent.com/u/1361894?v=4","gravatar_id":"","url":"https://api.github.com/users/graemechristie","html_url":"https://github.com/graemechristie","followers_url":"https://api.github.com/users/graemechristie/followers","following_url":"https://api.github.com/users/graemechristie/following{/other_user}","gists_url":"https://api.github.com/users/graemechristie/gists{/gist_id}","starred_url":"https://api.github.com/users/graemechristie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/graemechristie/subscriptions","organizations_url":"https://api.github.com/users/graemechristie/orgs","repos_url":"https://api.github.com/users/graemechristie/repos","events_url":"https://api.github.com/users/graemechristie/events{/privacy}","received_events_url":"https://api.github.com/users/graemechristie/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-19T14:17:12Z","updated_at":"2018-03-19T14:17:12Z","closed_at":null,"author_association":"NONE","body":"Currently, If we install the ASPNet Core 2.1 preview1-final Site Extensions using a resource template, or manually add a template via the Portal UI, the site extension will be removed the next time we deploy to a slot (using the powershell commandlets) and swap that slot into the production slot (using powershell commandlets.\r\n\r\nAs we do all of out deploys automatically, from CI, we cannot manually add a site extension after every deploy. \r\n\r\nWe currently need to re-add the site extension using a [hacky script](https://stackoverflow.com/questions/43693245/how-to-add-an-azure-app-service-extension-via-powershell) \r\n\r\nCurrently, using slots and CI to deploy to Azure App Services feels like a very second class experience.\r\n\r\nIs the site extension method just required as this is a preview release ? Or are we going to need to jump through these hoops for the full release ?\r\n\r\nCould we consider moving to a process of using app settings rather than site extensions as the PHP/Node engines do ?"}}
{"actor":{"display_login":"graemechristie"}}