I would like to propose a new feature for the Snapin management system: the ability to define a sequential execution order for a list of snapins, with the option to stop the queue if one of them fails.
Current Behavior:
Currently, snapins are assigned and executed, but there is no native way to ensure that a specific chain of snapins executes in a strict order where subsequent tasks depend on the success of the previous ones.
Proposed Feature:
Sequential Grouping: Allow users to create "Snapin Groups" or define a sequence index for assigned snapins.
Stop-on-Failure: Add a toggle in the snapin task configuration: "Abort execution sequence on failure". If enabled, if a snapin returns a non-zero exit code, the FOG client should stop the sequence and report the failure.
Enhanced Logging: Provide a clear log entry in the FOG web interface indicating exactly which snapin failed in the sequence, including the exit code provided by the client.
Use Case:
This would be extremely useful for complex software deployments where dependencies are required. For example:
Installing a prerequisite (e.g., a specific runtime) → If it fails, do not attempt to install the main application.
Running configuration scripts that rely on the successful completion of an installer.
Additional Information:
Is there currently a recommended way to achieve this using standard FOG functionality (e.g., via post-download scripts or complex batch files)?
If not, I am interested in hearing the maintainers' perspective on how this could be architecturally implemented within the FOG client/server communication flow.
I would like to propose a new feature for the Snapin management system: the ability to define a sequential execution order for a list of snapins, with the option to stop the queue if one of them fails.
Current Behavior:
Currently, snapins are assigned and executed, but there is no native way to ensure that a specific chain of snapins executes in a strict order where subsequent tasks depend on the success of the previous ones.
Proposed Feature:
Sequential Grouping: Allow users to create "Snapin Groups" or define a sequence index for assigned snapins.
Stop-on-Failure: Add a toggle in the snapin task configuration: "Abort execution sequence on failure". If enabled, if a snapin returns a non-zero exit code, the FOG client should stop the sequence and report the failure.
Enhanced Logging: Provide a clear log entry in the FOG web interface indicating exactly which snapin failed in the sequence, including the exit code provided by the client.
Use Case:
This would be extremely useful for complex software deployments where dependencies are required. For example:
Installing a prerequisite (e.g., a specific runtime) → If it fails, do not attempt to install the main application.
Running configuration scripts that rely on the successful completion of an installer.
Additional Information:
Is there currently a recommended way to achieve this using standard FOG functionality (e.g., via post-download scripts or complex batch files)?
If not, I am interested in hearing the maintainers' perspective on how this could be architecturally implemented within the FOG client/server communication flow.