Super v 5.1.0 - Need some help understanding temporary workflows and the ConfigTempOverride option for configuration profile

[dbsywnie84]

I posted this in the slack channel, but I wanted to post this on here since the files and info would probably be to huge. Has anyone tried out the Allow Temporary Configuration Override option? Does anyone know if this option is enable it would stop super from doing some kind of weird merger of the main super workflow pushed via JAMF and a temporary alternate workflow, so that it only executes everything in the temporary alternate workflow? I did some testing last week on a Mac computer and the temporary workflow produced some unexpected results.

This is what I have going for the temporary workflow via CLI:

/usr/local/bin/super --config-edit=companysuper_upgrade_def --verbose-mode --install-macos-major-upgrades --deferral-timer-default=180 --deferral-timer-menu=60,120,180,240,1440 --deferral-timer-focus=240 --deferral-timer-error=30 --deferral-timer-workflow-relaunch=1440 --schedule-zero-date-release --display-unmovable=DIALOG,DEADLINE,ERROR --display-notifications-centered=DEADLINE,ERROR --auth-ask-user-to-save-password --display-icon-size=96 --display-icon-file=/Library/Management/super/companylogo.png --display-accessory-type=HTML --display-accessory-default-file=/Library/Management/super/companyupdater.html --display-accessory-macos-major-upgrade-file=/Library/Management/super/companyupgrader.html --deadline-date-focus=2025-11-21:06:00 --deadline-date-hard=2025-11-28:18:00

I apologize for the super.log file and the other attachments. I tried my best to delete, as much unnecessary info, as I could to help with troubleshooting.

Original Plist File that is pushed out via Jamf

Default Plist Pushed via Jamf .txt

Alt Workflow Plist File

Local com.macjutsu.super plist file (Merged result after running super --config-start-temp=companysuper_upgrade_def)

super.log file from run

super.log

[Macjutsu]

First, it's much easier to gather this information using sudo super --config-status.

Second, if your going from any older version of super to v5.1.0-rcX then you should also run --reset-super to clear any cached settings.

Finally, the expected behavior is that super evaluates every single setting attribute individually. This allows you define "infrequently chaning defaults" in your main and/or managed settings, and then you'd only specificy unique differences in your alternate configurations. In other words, this merge behavior is expected. This behavior will be documented in the updated Wiki by the final release of v5.1.0.