[GH-ISSUE #360] Community script library - enhancements to unique ID and managing community script library changes/deletes #2168

New issue

Closed

opened 2026-03-14 02:51:20 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 02:51:20 +03:00

Owner

Originally created by @silversword411 on GitHub (Apr 2, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/360

From discord chat, my understanding is community scripts on first install are converted to base64 and imported into the database. The unique key is the "name": field. If that is changed then it will think it's a new script and can break things.

First
Add new field in community_scripts.json
uuid: that will be the unique database identifier (need method of creating it the first time).

Second
Update script needs to be fixed so that:
All community scripts database entries unique key is changed from name: to uuid:

Third
Update script needs to be fixed so that:
If a community script is deleted (uuid: no longer there) and is not in use purge from local database
OR
If a community script is deleted (uuid: no longer there) AND it's currently in use in the local install the script should be converted from a community (unmodifiable) script to a userdefined script (so we don't break existing automation profiles).

Originally created by @silversword411 on GitHub (Apr 2, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/360 From discord chat, my understanding is community scripts on first install are converted to base64 and imported into the database. The unique key is the "name": field. If that is changed then it will think it's a new script and can break things. First Add new field in `community_scripts.json` `uuid:` that will be the unique database identifier (need method of creating it the first time). Second Update script needs to be fixed so that: All community scripts database entries unique key is changed from `name:` to `uuid:` Third Update script needs to be fixed so that: If a community script is deleted (uuid: no longer there) and is not in use purge from local database OR If a community script is deleted (uuid: no longer there) AND it's currently in use in the local install the script should be converted from a community (unmodifiable) script to a userdefined script (so we don't break existing automation profiles).