A first implementation should be made to see how superuser might work.
From the parent issue:
Have two developers on the same physical host run a single process manager, and attempt to run the standard sets of commands. The unified shell already provides the infrastructure to connect to an existing process manager. This will need to be validated and updated if necessary.
It appears that for now the way we can do this is to have a 'superuser' that launches everything. So if i connect to a PM session that Pawel has made and I send a command, it will be executed using Pawel's account since he is a super user.
This basic implementation works, but at some point in the future we should probably upgrade this and have a proper 'drunc superuser' account or similiar
A first implementation should be made to see how superuser might work.
From the parent issue:
Have two developers on the same physical host run a single process manager, and attempt to run the standard sets of commands. The unified shell already provides the infrastructure to connect to an existing process manager. This will need to be validated and updated if necessary.
It appears that for now the way we can do this is to have a 'superuser' that launches everything. So if i connect to a PM session that Pawel has made and I send a command, it will be executed using Pawel's account since he is a super user.
This basic implementation works, but at some point in the future we should probably upgrade this and have a proper 'drunc superuser' account or similiar