Populate EA via a separate script?

Why would you want to scope an extension attribute instead of scoping a policy that contains a script?

We use EAs to collect information and scripts to perform actions. Some of the information we want to collect is not global so it's not necessary to run that EA on all computers which is why it would be nice to be able to scope EAs.

Why not simply populate the EA using a script directly ?
Rather then using this "double method" ?

After all if you are going to source from a script to begin with, I see no point in introducing an intermediate stage..
- Just directly populate the EA from a script.

Yes you do have to run this on all computers, but the script could start with some condition that creates a shortcut exit on those machines that it's not to apply to.

Currently there is no way to scope EA's, and no 'contrived' way that I can think of.
The best method I can come up with for now is the "short-cut exit"

If necessary, if the conditions are really complex, then you could simplify by creating another script to set a client-side flag, and then test for that as the short-cut exit condition for the EA.

That would make the EA a very light-weight process, that could easily be run on all clients, with minimal impact.
So I think that would be the way to go.

@PeterClarke
I think what you are saying makes the most sense for now. I already have the script perform some conditional checks before it proceeds. I just wanted to throw the idea out there to see if it was possible. Thanks for the feedback.

I have started using this. It allows for populating EAs.
You will need to package the logging file and deploy it before the script runs. But its works great!

https://community.jamf.com/t5/jamf-pro/your-internal-beta-test-program-opt-in-opt-out-via-self-service/td-p/147311