BlueprintFramework
Autonomous version of scripts
Allows developers to include an "autonomous" version of their scripts (install/remove). This autonomous version is quite literally just a clone of the original version, and relies on developers to be smart & not require human interaction in the autonomous scripts.
Along with this, a new conf.yml option canRunAutonomous has been introduced, defaulting to true, requires no action from developers upfront. However, if their addon cannot function without human interaction, they can set this to false, and if the extension is attempted to be installed with the autonomous mode, it will reject & exit the process before any changes are made (i think).
To trigger the autonomous mode, you just use -script. For example, /usr/local/bin/blueprint -i extmanager.blueprint -script. That -script can be anywhere after the -i or -r, it will not be counted as an extension to remove.
Usecase:
Does this expose an environment variable to scripts indicating that they are running "autonomously"?
I simply made it run a completely separate script, autonomous_install.sh and autonomous_remove.sh, but that seems like a better option