governed-job-launcher

Secure job execution integrates risk assessment, check mode validation, and approval gates to ensure compliance. This approach requires explicit user approval for high-risk operations and provides rollback capabilities using relaunch or alternate templates if the job fails.

Check mode in job execution performs a dry run to validate operations without making actual changes. It ensures that templates and parameters are correct before proceeding to full execution, preventing unintended modifications to managed systems.

Yes, you can enforce governance controls by setting up approval gates that require explicit user approval before high-risk job executions proceed. This ensures that critical operations are manually verified before any changes are applied.

Assess execution risks by integrating a risk assessment analyzer before job launch. This evaluates the potential impact of the operation, categorizing risk levels to determine whether check mode validation or explicit approval is required before execution.

Yes, governed-job-launcher depends on execution-risk-analyzer for assessing risks and aap-mcp-validator for validation. These integrations provide the necessary risk evaluation and compliance checks required to securely execute jobs.

If a job execution fails, rollback options include relaunching the job with corrected parameters or using alternate templates. This ensures that managed systems can be restored to a compliant state after a failed operation.