Hi,
I did some googling and checked the docs, but haven't found a way to mount multiple non-sibling folders into the VM. I know a workaround is to mount a common parent to several folders. But that imposes some limitations in how your repos are laid out, and doesn't allow you to easily exclude some repos from an agent but include some other for another.
My current example is an agent working on a datalake models repo that requires read-only access to the backend repo so it can get the DB models and business logic from.
I was thinking that I'll be cool to make it possible to specify multiple mount points for a single VM. Ideally allowing to make them rw/ro, so that changes to any read-only repo are discarded from diffs automatically.
I imagine this could break how multiple local .broodbox.yamls work, so this might need some sort of way to decide which one to use. Maybe a way to override the location with a --local-config flag (similar to the global equivalent works).
What are your thoughts?
Hi,
I did some googling and checked the docs, but haven't found a way to mount multiple non-sibling folders into the VM. I know a workaround is to mount a common parent to several folders. But that imposes some limitations in how your repos are laid out, and doesn't allow you to easily exclude some repos from an agent but include some other for another.
My current example is an agent working on a datalake models repo that requires read-only access to the backend repo so it can get the DB models and business logic from.
I was thinking that I'll be cool to make it possible to specify multiple mount points for a single VM. Ideally allowing to make them rw/ro, so that changes to any read-only repo are discarded from diffs automatically.
I imagine this could break how multiple local
.broodbox.yamls work, so this might need some sort of way to decide which one to use. Maybe a way to override the location with a--local-configflag (similar to the global equivalent works).What are your thoughts?