You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 4, 2022. It is now read-only.
When servicing cloud boxes in LCS or even running Deployment.Setup.exe to run DbSync on a VHD/devbox, the servicing operation does not know we're using Cloud and Edge nor how to communicate with the created Azure blob storage.
During environment configuration, we should update Deployment.Setup.exe.config (not the full name of the file) such that it has our ScaleUnit.Enabled, ScaleUnit.InstanceID and DbSync.TriggersEnabled parameters and also the encrypted variant of the AzureStorageConnectionString in it (similar to what we put in web.config.
LCS-invoked servicing fails due to this misbehaving.
Acceptance Criteria
Can service LCS Cloud-hosted developer Spoke with packages from LCS portal without error.
DbSync, Deployment.Setup.exe and the kernel know we're in a Scale Unit context and has access to the storage account of the scale unit.