Re: [Bro-Dev] package manager progress

> Right now, packages don’t get downloaded via the submodule, they are > cloned directly from the package’s full git URL (which git just > happens to encoded within the submodule). > > So this means only packages a user is interested in end up getting > downloaded. I'm not 100% following. Isn't

Re: [Bro-Dev] package manager progress

> On Jul 24, 2016, at 3:45 PM, Siwek, Jon wrote: > > * Add a way for package’s to define “discoverability metadata”. Kind of related to this, I think we need to define some basic rules for package naming. This can help discoverability and also namespacing issues. Right

Re: [Bro-Dev] package manager progress

> On Jul 25, 2016, at 10:18 AM, Matthias Vallentin wrote: > >> * Add a way for package’s to define “discoverability metadata”. >> >> E.g. following the original plan for this would involve putting >> something like a “tags” field in each package’s pkg.meta file, but the >>

Re: [Bro-Dev] Broker data store API

The number of key/values would depend on the scale of the environment in the case of the authentication framework. In my last implementation... it was one record per user/host pair... which could scale into the tens of thousands of key/value pairs pretty quickly. I haven't looked at that stuff

Re: [Bro-Dev] package manager progress

> On Jul 25, 2016, at 6:53 AM, Jan Grashöfer wrote: > >> * Add a way for package’s to define “discoverability metadata”. >> >> E.g. following the original plan for this would involve putting something >> like a “tags” field in each package’s pkg.meta file, but the

Re: [Bro-Dev] Broker data store API

> I can't speak to whether or not it is 'needed', but I have had desire > to use it in the past... The only thing preventing me from doing it > was the fact that Broker is currently a fast moving target. Good to know. Scott Campbell also uses the current version of Broker in his projects and

Re: [Bro-Dev] package manager progress

> The package manager client is at a point now where I think it would be > usable. Cool! > * Add a way for package’s to define “discoverability metadata”. > > E.g. following the original plan for this would involve putting > something like a “tags” field in each package’s pkg.meta file, but

Re: [Bro-Dev] package manager progress

Amazing work! I really like the package manager and I am looking forward to contributing a script. > * Add a way for package’s to define “discoverability metadata”. > > E.g. following the original plan for this would involve putting something > like a “tags” field in each package’s pkg.meta

Re: [Bro-Dev] Broker data store API

I can't speak to whether or not it is 'needed', but I have had desire to use it in the past... The only thing preventing me from doing it was the fact that Broker is currently a fast moving target. Generally speaking, I was wanting to do it so that I could save state between cluster restarts