A BATS test could be done to upload a config that Solr has but that which isn't uploaded by default (and only _default is by default). So techproducts seems like the clear choice. These are just 2 system properties; one for the path (e.g. "solr/server/solr/configsets/sample_techproducts_configs/conf"), the other to name it (e.g. "techproducts").
Consider assigning a GitHub Copilot Agent or Google Jules to this task. I've been using Copilot agents over the last few days and it's worked remarkably well so far. https://github.com/copilot/agents You have to point it at your fork and not apache/solr but ultimately you can create the PR to apache/solr from the very same branch. On Mon, Aug 25, 2025 at 8:43 AM Eric Pugh <ep...@apache.org> wrote: > Could you share an example usage? I'd love to get a .bats test in for > starting Solr with bootstrap_confdir and/or DEFAULT_CONFDIR in Solr 10 > > Then maybe we could remove bootstrap_conf? > > > > On 2025/08/24 04:58:38 David Smiley wrote: > > I've used bootstrap_confdir and env var DEFAULT_CONFDIR (as recently as > > yesterday quite literally) for convenient ways of bootstrapping a custom > > Docker image with one's own configset. In that scenario (embedded ZK), > > it's awkward to attempt to use zkcli upconfig after Solr starts since > > there's no hook/script to execute something after Solr starts. > > > > On Sat, Aug 23, 2025 at 9:58 PM Mark Miller <markrmil...@gmail.com> > wrote: > > > > > These where system properties that allowed automated config set upload > > > before better options came along. This was pre collection API or other > > > scripts that let you upload a config set. They were probably largely > added, > > > like internal zk mode, for the “demo” - a series of commands on the > wiki > > > you could run to bring up a working cloud cluster without any other > manual > > > steps. > > > > > > I believe one of them let you specify a directory to upload and the > other > > > would look at solr.xml and upload the config sets for all configured > cores. > > > > > > I believe this code was rooted in ZkController or maybe ZkContainer > > > initially. I suppose for back compatibility, eventually support was > moved > > > to ConfigSetService. If they don't currently work, at some point they > must > > > have been broken. They are no longer mentioned in the docs, and the > > > functionality they provided was long ago superseded by more modern > options. > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org > For additional commands, e-mail: dev-h...@solr.apache.org > >
