From 2c01ffb7541cae303be0a4c3c716a883a26fb9a6 Mon Sep 17 00:00:00 2001 From: Amndeep Singh Mann Date: Mon, 20 Dec 2021 12:31:26 -0500 Subject: [PATCH] provided a different example status for a profile in an exec_json since 'loaded' is different from the other usual possibilities and also is going to be the presumably most common status Signed-off-by: Amndeep Singh Mann --- lib/inspec/schema/exec_json.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/inspec/schema/exec_json.rb b/lib/inspec/schema/exec_json.rb index 0cdf1dd98..d2bf3e9e3 100644 --- a/lib/inspec/schema/exec_json.rb +++ b/lib/inspec/schema/exec_json.rb @@ -102,7 +102,7 @@ module Inspec # These are generated at runtime, and all except status_message and skip_message are guaranteed "sha256" => Primitives.desc(Primitives::STRING, "The checksum of the profile."), - "status" => Primitives.desc(Primitives::STRING, "The status. Example: skipped."), + "status" => Primitives.desc(Primitives::STRING, "The status. Example: loaded."), # enum? loaded, failed, skipped "status_message" => Primitives.desc(Primitives::STRING, "The reason for the status. Example: why it was skipped or failed to load."), "skip_message" => Primitives.desc(Primitives::STRING, "The reason for skipping if it was skipped."), # Deprecated field - status_message should be used instead. "controls" => Primitives.desc(Primitives.array(CONTROL.ref), "The set of controls including any findings."),