Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set current working directory for VOLTTRON and VOLTTRON agents #167

Open
schandrika opened this issue Mar 23, 2023 · 0 comments
Open

Set current working directory for VOLTTRON and VOLTTRON agents #167

schandrika opened this issue Mar 23, 2023 · 0 comments
Assignees

Comments

@schandrika
Copy link
Contributor

Is your feature request related to a problem? Please describe.
When VOLTTRON or agents create files in a configured path, then relative paths are relative to where volttron was started from.
This could cause the issue in several situations for example

  1. When more than one instance of volttron is started from the same location with the command VOLTTRON_HOME=<some path> volttron -vv -l volttron.log & at say different point in time
  2. When sqlitehistorian is run with a configuration pointing to a relative path or with just a file name without path

Describe the solution you'd like
Set current working directory of VOLTTRON process to $VOLTTRON_HOME. Set current working directory of agents $VOLTTRON_HOME/agents/

Describe alternatives you've considered
We could always use absolute path to avoid this issue but that is not very convenient
Additional context
When porting agents from monolithic. Care should be taken to verify relative paths in configuration. But modular version of VOLTTRON is not backward compatible with monolithic code, we can simply add it to porting instruction

@schandrika schandrika self-assigned this Mar 23, 2023
schandrika added a commit to schandrika/volttron-core that referenced this issue Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant