Script output Best Practice Contracts
retained text
Hi Devops! I’m putting together an automation orchestration engine and I want to mature the team by standardizing script output across bash, python, powershell, tofu, etc. So looking at a JSON output contract that anyone creating a script can adhere to. Then everyone would consume the same format. (The dream right?) - Operation name - Host - Execution status (success, fail, warning, etc) - Structured result summary - Errors - Duration - Run ID (UUID)? - A schema version (requires a lot of upkeep but can eliminate headaches down the road if maintained. If maintained being key word here lol.) I’ve been searching around but want to hear from the experts who live in this stuff. Is there any universal or open standard people are using to define these ? Would rather not build it myself if something people have already settled on. Thanks for your input.
document fetched 2026-10-10 00:25 · canonical https://reddit.com/r/devops/comments/1x1d85q/script_output_best_practice_contracts