[BUG] extension_modules folder is always prepended with root dir
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
When
extension_modules: myextensions
Salt always starts from the root dir (captured by strace):
stat("/myextensions/utils", 0x7ffd19a011d0) = -1 ENOENT (No such file or directory)
Thus making impossible not to hardcode extensions path into salt .conf file.
So I have to do:
extension_modules: /srv/salt/myextensions
What I want is to be able to put a relative name like:
extension_modules: myextensions
And salt would find it related to working directory.
When salt does like this it makes possible just to copy working folder to any place and work with it.
3001
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the configuration with extension_modules: myextensions and observing the path lookup described by strace. Trace where Salt resolves extension_modules; done means a relative path is resolved from the working directory while absolute paths continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100