search

threefoldtecharchive / 0-robot

Distributed live cycle management system
Apache License 2.0
0 stars 0 forks source link

robot server start --config-repo XYZ changes previously set jumpscale repo globally #12

Closed rkhamis closed 5 years ago

rkhamis commented 6 years ago

Issue migrated from [https://api.github.com/repos/zero-os/0-robot/issues/236](), opened by @yveskerwyn

When starting a zero-robot like this:

config_repo='ssh://git@docs.greenitglobe.com:10022/yves/my_jsconfig'
zrobot server start --listen :6600 --template-repo $zos_templates --data-repo $data_repo --config-repo $config_repo

the path of the config repo is changed for the whole system (globally):

j.tools.configmanager.path
-> '/Users/yves/code/docs/yves/my_jsconfig'

This while existing JumpScale interactive shells still use the previously set config repo:

j.tools.configmanager.path
->  '/Users/yves/code/docs.grid.tf/yves/jsconfig'  ## NOTE THE DIFFERENCE

Expected behavior was that the robot would use a sandboxed config repo, instead of changing it globally.

rkhamis commented 6 years ago

commented by @zaibon @yveskerwyn This behavior is the expected behavior. I don't know what a sandboxed config repo is. That sounds like something that could be used here indeed to help development. But in production this is not a real problem anyhow.