You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of one big all-or-nothing switch, finer control over various
dangerous action is needed. Users can still allow everything, with
`--feeling-safe`, or allow individual dangerous functionalities.
Copy file name to clipboardExpand all lines: tests/plan/select/test.sh
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -45,12 +45,12 @@ rlJournalStart
45
45
done
46
46
47
47
rlPhaseStartTest "tmt plan ls --condition requires --feeling-safe"
48
-
rlRun -s "TMT_FEELING_SAFE=0 tmt plan ls --condition 'True'" 2
49
-
rlAssertGrep "requires the '--feeling-safe' option"$rlRun_LOG
48
+
rlRun -s "unset TMT_FEELING_SAFE; tmt plan ls --condition 'True'" 2
49
+
rlAssertGrep "'--condition' command-line option is allowed only with the '--allow-unsafe-behavior=cli.condition' or '--feeling-safe' option."$rlRun_LOG
50
50
rlPhaseEnd
51
51
52
-
rlPhaseStartTest "tmt plan ls --condition with --feeling-safe"
53
-
rlRun -s "tmt --feeling-safe plan ls --condition 'True'"
52
+
rlPhaseStartTest "tmt plan ls --condition with --allow-unsafe-behavior=cli.condition"
53
+
rlRun -s "tmt --allow-unsafe-behavior=cli.condition plan ls --condition 'True'"
0 commit comments