Add backwards compatibility clarification on CLI tooling output (#29961)
Json output should remain consistent to avoid breaking automation; however, we want to be free to update human-reader-centric output to remove output as it becomes deprecated.
This commit is contained in:
parent
4cc07a176e
commit
9b13b90066
|
@ -149,3 +149,9 @@ software releases.
|
||||||
|
|
||||||
If a new attack vector is discovered in existing code, the above processes may be
|
If a new attack vector is discovered in existing code, the above processes may be
|
||||||
circumvented in order to rapidly deploy a fix, depending on the severity of the issue.
|
circumvented in order to rapidly deploy a fix, depending on the severity of the issue.
|
||||||
|
|
||||||
|
#### CLI Tooling Output
|
||||||
|
|
||||||
|
CLI tooling json output (`output --json`) compatibility will be preserved; however, output directed
|
||||||
|
for a human reader is subject to change. This includes output as well as potential help, warning, or
|
||||||
|
error messages.
|
||||||
|
|
Loading…
Reference in New Issue