I +1 for switching to bazel for better structure and procedure to compile the topology. I believe a working example of python topology is necessary, and require a good angle to show how to utilise the elements of Heron.
Regards J, Windham Wong OSWE, OSCP, GCIA, Specialist in Cybersecurity Co-Founder, Managing Partner of Stormeye.io, Hong Kong Managed Security Operation Center Limited Specialist in Cybersecurity, Log Management and SIEM System Email // [email protected] (https://link.getmailspring.com/link/[email protected]/1?redirect=mailto%3Awindham.wong%40stormeye.io&recipient=ZGV2QGhlcm9uLmFwYWNoZS5vcmc%3D) Phone // +852_3590_2212_|_+852_9832_0707 (tel:+85235902212) Fax // +852_3590_2202 (tel:+852_3590_2202) On 9月 11 2021, at 8:07 早上, Saad Ur Rahman <[email protected]> wrote: > Hi Josh, > > This would be a massive boon to adoption. If all you need to do is install > dependencies, perform a Git pull, and then kick off a build life becomes > rather easy. > On 2021/09/10 22:33:49 Josh Fischer wrote: > > Hey all, > > > > As part of increasing community adoption we need to make it easier to work > > with heron, work in an IDE and etc. I’m thinking of starting to look this > > weekend switching from pex_rules to native bazel Python rules. Anyone see > > any issues with this? > > -- > > Sent from A Mobile Device > > >
