Also - sounds like a really neat blog post
# general
d
Also - sounds like a really neat blog post
c
Thanks! I know it's something the community has requested. While AWS is an option and I am considering it..... I am not thrilled about the cost. It's very $$$$$ to run a macOS VM in AWS.
z
GitHub Actions macOS runner in a public repo?
πŸ‘ 1
s
Also had some succes with the method @zwass is describing.
d
nice, I didnt realize GH actions had added MacOS
z
Yes and totally free for public repos πŸ˜„
πŸ’― 1
d
that seems probably more affordable
z
I suppose that may not play nice with the "Gitlab" angle of this blog post
Example usage of my own.
c
It’s good to know Github actions support MacOS. It might a good complimentary addition. But I would like to stick with Gitlab.
z
I do manual testing with macOS VMs on macOS (this is allowed).
w
πŸ‘€ 1
🦜 2
z
Oh my. Life changer if it works. Thank you @WS!
w
πŸ™‚
c
So I had an epiphany last night on this topic. Wanted to get some feedback on the idea. So the reason for spinning up a macOS VM with a Gitlab runner is to test an Osquery macOS specific config. As discussed above there is no good way to do this. So my epiphany is based on an assumption. If you want to test a macOS specific Osquery config you probably have macOS endpoints connected to Fleet. Therefore, instead of using a Gitlab runner to test my config, I would parse all the queries out of the config, and use the FleetCTL tool to test the queries on macOS endpoints.
w
so using an actual host?
c
Yes.
w
are you going to use a test machine? because then you have to account for it going offline right
if you had an unlimited budget, would you use the macos vm on AWS?
c
The idea of using Fleet would be to query live macOS hosts that ideally would be a set of test hosts and online.
I think running a macos based VM in AWS could be a good method. However, if your Gitlab instance is behind NAT it creates a roadblock.