deleting scripts/EAs?

[christozlowski]

I noticed that if a directory is deleted then the script skips it and doesn't do anything.

# If directory is deleted, mark it as processed and skip all its files
if [[ ! -d "$dir" ]]; then
echo "[INFO] Skipping deleted directory: $dir"
processed_dirs[$dir]=1
continue
fi

Are the deleted scripts/EAs handled elsewhere or do they just live on the Jamf Pro server until manually deleted?

[74k1]

Hi @christozlowski

Thanks for pointing this out. You're right, we do silently skip any directory that has been deleted.
This is intentional: it prevents a single mistake from nuking half your Jamf instance. In practice, the orphaned scripts/EAs just sit on Jamf Pro until you (or another admin) removes them manually through the web UI.

I just noticed I never spelled this out anywhere in the docs. I’ll get that added asap.

That said, a "delete what's gone" mode would be trivial to implement. I can see how this can be useful, but then again, I'm thinking of the consequences that it could cause if handled improperly. (existing policies will just not find the script anymore, therefore those would be unneeded as well, etc.)
If it’s something you'd find useful, feel free to keep this issue open as a feature request.

The rest of the community can "vote" on it with a 👍 reaction, and if enough people want it I'll add a flag (--cleanup or similar) that actually deletes the missing scripts/EAs.

[christozlowski]

That makes sense. It would be nice to have, but I get that it's difficult to get right.