One of the benefits of the git2jss workflow is having scripts/EAs under version control - git shows a history of all changes, so we can see when and by whom changes were made. In order for this to be really effective, we need to modify permissions on Jamf Pro so that admins cannot make changes directly in Jamf.
However, changing permissions on Jamf also prevents changes being made to non-script EAs. The sync.py and download.py scripts specifically exclude these from their scopes, so that they can't be changed using the git workflow. As a result, we end up not being able to change these EAs at all (unless we revert the permissions settings, which isn't great).
Could we please include non-script EAs in scope? I think this could be done by just removing the checks which skip EAs if no script is found, but I guess we might want to make it an option that can be enabled with a script attribute. (Also not sure if it would require changes to the JamfObject class). I'm happy to have a crack at a PR, if appropriate.
One of the benefits of the git2jss workflow is having scripts/EAs under version control - git shows a history of all changes, so we can see when and by whom changes were made. In order for this to be really effective, we need to modify permissions on Jamf Pro so that admins cannot make changes directly in Jamf.
However, changing permissions on Jamf also prevents changes being made to non-script EAs. The sync.py and download.py scripts specifically exclude these from their scopes, so that they can't be changed using the git workflow. As a result, we end up not being able to change these EAs at all (unless we revert the permissions settings, which isn't great).
Could we please include non-script EAs in scope? I think this could be done by just removing the checks which skip EAs if no script is found, but I guess we might want to make it an option that can be enabled with a script attribute. (Also not sure if it would require changes to the JamfObject class). I'm happy to have a crack at a PR, if appropriate.