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
If you try to import an existing application and the logged user is not the same as the manager of the application you get a Walkback. (Even when MonticelloLoader appSuperGroupSetting: #world ) .
See attached stack trace: Manager-stack.txt
Steps to reproduce:
Create and version an application with the same of some app to import (by default it will be managed by LibrarySupervisor) and change the privileges so superGroup = #world.
Try importing a package that will end up in that application, and you will get something like: 'Base edition for BuoySUnitModel is managed by Supervisor. You are currently gcotelli and cannot create new editions of the application.'
It seems that the importer doesn't take into account the privileges, just check that the current user is the same as the application manager, even if the current user will have the required permissions to create and release editions in the app.
The text was updated successfully, but these errors were encountered:
It will honor the SuperGroup setting of the application when checking privileges, and also set the newly created edition with the setting defined in the TonelLoader or the previously existing setting if it's absent in the setting.
Hi @gcotelli, we're doing a cleanup pass on pending issues and this seems already solved.
Did you try loading from a Tonel repository with the above mentioned setting?
If you try to import an existing application and the logged user is not the same as the manager of the application you get a Walkback. (Even when
MonticelloLoader appSuperGroupSetting: #world
) .See attached stack trace:
Manager-stack.txt
Steps to reproduce:
MonticelloLoader appSuperGroupSetting: #world
'Base edition for BuoySUnitModel is managed by Supervisor. You are currently gcotelli and cannot create new editions of the application.'
It seems that the importer doesn't take into account the privileges, just check that the current user is the same as the application manager, even if the current user will have the required permissions to create and release editions in the app.
The text was updated successfully, but these errors were encountered: