* Fleet podcast episode 7 images upload
* Initial article post
Still need to update podbean links once available
* Removing due to incorrect title
* Removing due to incorrect title
* Reuploading correct thumbnails
* Update the-future-of-device-management-ep7.md
* Updated podbean link
* Unused image - removing
* Update articles/the-future-of-device-management-ep7.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update articles/the-future-of-device-management-ep7.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Update the-future-of-device-management-ep7.md
* Update articles/the-future-of-device-management-ep7.md
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
* Initial work on sandbox data pipeline
* Update python code to have preliminary code
* Added in final code for sandbox-data.
Huge delay because I needed to double check licensing
We don't have a `matrix.go-version` defined, so the task was using
`go1.17.13` as the default.
This explicitly sets the version to `go1.19.1`, I didn't use a `matrix`
definition because at least for now, we only want to run this test using a
single Go version.
Since I was there, I also updated test-native-tooling-packaging.yml to
use `go1.19.1` too.
* update deployment guide and add additional descriptions/comments for terraform resources
* add architecture diagram to deployment guide
* cleaning up more terraform deployment documentation
* Create .trivyignore
Adding original trivy ignore file. Working to resolve/document more of the findings, especially around go.mod. Will add a github action as well.
* Adding default trivy scan for testing
* Update trivy_scan.yml
Making it manual + daily for now
* Update trivy_scan.yml
updating name
* Renamed + configured Trivy scan
This improves osquery-perf with support for a more realistic orbit + fleet desktop simulation as described in #8212
This was based on the work done by @sharvilshah in his branch.
Previously, the primary ip was determined using the interface with the most traffic. This had a few issues and required explicitly filtering out certain interfaces that we don't want eg loopback, docker.
Instead, use the default route to determine the primary (private) ip. If there are multiple, use the one with the lowest metric and prefer ipv4 addresses.
Robert Fairburn