[Package Issue]: DBeaver.DBeaver not respecting machine install scope defined in settings.json #135726
Closed
2 tasks done
Labels
Area-Manifest
This may require a change to the manifest
Area-Scope
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Milestone
Please confirm these before moving forward
Category of the issue
Installation issue.
Brief description of your issue
The installer.yaml file for DBeaver has been changed in version 23.3.2 and removed the explicit user and machine codeblocks. For some reason the app now get's installed by default in the user scope unless --scope machine is passed.
If I don't pass the scope it get's installed in user context even though I have configured the settings.json file where I explicitly set that everything must be installed in machine context if possible. (This works fine for other apps)
This currently breaks installing the app using Intune where the system account is used to install the app (it now installs it in the user profile of the system account making the app unusable for the logged on user).
This worked fine before.
Steps to reproduce
winget install --exact dbeaver.dbeaver --silent --accept-package-agreements --accept-source-agreements
Actual behavior
DBeaver is installed in user context even though settings.json has been configured in the defaultState (System) / LocalState (User) directories.
Expected behavior
DBeaver get's installed in machine context. (Corporate devices should not use user installed apps wherever possible in my opinion).
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: