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
Copy file name to clipboardExpand all lines: docs/source/user_guide/cli/opctl/_template/jobs.rst
+6-6
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,12 @@ Prerequisite
7
7
8
8
:doc:`Install ADS CLI <../../quickstart>`
9
9
10
-
Running a Pre Defined Job
10
+
Running a Pre Defined Job
11
11
-------------------------
12
12
13
13
.. code-block:: shell
14
14
15
-
ads opctl run -j<job ocid>
15
+
ads opctl run --ocid<job ocid>
16
16
17
17
Delete Job or Job Run
18
18
---------------------
@@ -36,15 +36,15 @@ Stop a running cluster using ``cancel`` subcommand.
36
36
**Option 1: Using Job OCID and Work Dir**
37
37
38
38
.. code-block:: shell
39
-
40
-
ads opctl cancel -j <job ocid> --work-dir <Object storage working directory specified when the cluster was created>
39
+
40
+
ads opctl cancel <job ocid> --work-dir <Object storage working directory specified when the cluster was created>
41
41
42
42
**Option 2: Using cluster info file**
43
43
44
44
Cluster info file is a yaml file with output generated from ``ads opctl run -f``
45
45
46
46
.. code-block:: shell
47
-
48
-
ads opctl cancel -j <job ocid> --work-dir <Object storage working directory specified when the cluster was created>
47
+
48
+
ads opctl cancel <job ocid> --work-dir <Object storage working directory specified when the cluster was created>
49
49
50
50
This command requires an api key or resource principal setup. The logs are streamed from the logging service. If your job is not attached to logging service, this option will show only the lifecycle state.
0 commit comments