Differences

This shows you the differences between two versions of the page.

--- public:99_annexes:annex-b-terms-and-definitions:n:non-interactive_execution [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:n:non-interactive_execution to public:99_annexes:annex-b-terms-and-definitions:n:non-interactive_execution nick_dido
+++ public:99_annexes:annex-b-terms-and-definitions:n:non-interactive_execution [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== Non-Interactive Execution ======
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 ===== Discussion =====
@@ Line 9: / Line 9: @@
 The executing process receives its required inputs through controlled configuration, files, environment values, credentials, interfaces, or other predefined mechanisms.
-Non-Interactive Execution supports automation by allowing a command, workflow, or [[private:99_annexes:annex-b-terms-and-definitions:b:build_pipeline|Build Pipeline]] to run without an attending operator.
+Non-Interactive Execution supports automation by allowing a command, workflow, or [[public:99_annexes:annex-b-terms-and-definitions:b:build_pipeline|Build Pipeline]] to run without an attending operator.
 Within Crucible, non-interactive commands return defined exit status values and produce structured records that allow a continuous-integration or continuous-delivery system to determine whether an operation succeeded or failed.