When we run a typical policy with the Jamf Pro Framework, it runs as root by default, which is good 90% of the time because that’s what most Mac installers want, but not Brew. Did you notice that there’s no sudo on the installation command? The authors don’t want you to give their tool permanent admin permissions - they’ll ask for them whenever they’re needed. There’s a bit of a catch that makes Brew installs different from most other apps. There’s a bunch of OS version and cpu-specific stuff in there. Don’t do it unless every machine you’ve got is identical. You could run the install and capture it with Jamf Composer. The disadvantage is that you have to trust the repo. The advantage of of the former is that you won’t have to do anything to keep your policy up to date with the latest version - the curl is always going to bring down the current version. You could just take that command and stick it in a Jamf Pro script as-is, or you could download the actual installer script from github, carefully review it, and then put that into a Jamf Pro script. Then take that thing you downloaded and run it as a bash script.
Basically, that says, “Download this URL, fail silently, don’t show progress, show errors, and redo the request if the location has moved.
