Re: ansible.cfg pathname setting
Chuck Lever <[email protected]>
| Newsgroups | dev.linux.lists.kdevops |
|---|---|
| Message-ID | <[email protected]> |
On 8/28/25 2:59 PM, Luis Chamberlain wrote: > On Thu, Aug 28, 2025 at 12:41:08PM -0400, Chuck Lever wrote: >> Any opinions about this idea? I can build it if folks agree to it. > > I tend to just run my own new make defconfig-foo in each directory for > each workload, so I have opinion on this, but it sounds like perhaps > a kconfig option is desirable, to perhaps opt-in to let it use current > working directory for the file? That's the basic idea. It feels like that would work better "just out of the shrinkwrap". > But if it was not generated then via > make then what would it use? Ie, if you're shaing a built .config to > other directories without making make then it sounds like a requirement > is to also share the generated ansible config? I think that's what I would have to do: include both the .config and an ansible.cfg in the kdevops branch pulled by each test runner. That seems to break the idea that the whole configuration is managed from .config. -- Chuck Lever