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/glossary.rst
+11-1
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,10 @@
66
66
- :code:`polling`, the value (in seconds) used to periodically contact the Aviso server
67
67
- :code:`auth`, the location to the Aviso authentication credentials file
68
68
69
+
.. note::
70
+
71
+
The `listener` parameter is expected to be a valid single line JSON string, enclosed in single quotes.
72
+
69
73
The value of the properties :code:`url`, :code:`schema`, :code:`polling`,
70
74
and :code:`auth` can be composed of :term:`Variables<variable>`. When
71
75
these properties are not provided, the following default values are used:
@@ -92,7 +96,9 @@
92
96
can be reloaded (without unqueuing the Task) by issuing an Alter change command with
93
97
the value :code:`reload` to the relevant Aviso attribute.
94
98
95
-
The authentication credentials file is expected to be in JSON format, following the `ECMWF Web API <https://www.ecmwf.int/en/computing/software/ecmwf-web-api>`_:
99
+
The authentication credentials file is expected to be in JSON format, following
100
+
the `ECMWF Web API <https://www.ecmwf.int/en/computing/software/ecmwf-web-api>`_
101
+
(this is conventionally stored in a file located at `$HOME/.ecmwfapirc`):
96
102
97
103
.. code-block:: json
98
104
@@ -104,6 +110,10 @@
104
110
105
111
Only the fields :code:`url`, :code:`key`, and :code:`email` are required; any additional fields are ignored.
106
112
113
+
The Aviso schema file is a JSON file that defines the event listener schema. This is used by both Aviso server
114
+
and client (thus, by ecFlow) to define the valid event types and request parameters used when polling for
115
+
notifications. The schema file path must be provided to the `schema` option (or via the `ECF_AVISO_SCHEMA` variable).
116
+
107
117
check point
108
118
The check point file is like the :term:`suite definition`, but includes all the state information.
Copy file name to clipboardexpand all lines: docs/python_api/AvisoAttr.rst
+21-6
Original file line number
Diff line number
Diff line change
@@ -12,26 +12,41 @@ An :term:`aviso` attribute, assigned to a :term:`node`, represents an external t
12
12
Although :term:`aviso` attributes can be set at any level (Suite, Family, Task), it only makes sense to assign aviso attributes to tasks, and only one aviso attribute per node is allowed.
Copy file name to clipboardexpand all lines: docs/ug/user_manual/text_based_suite_definition/external/aviso.rst
+16-6
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,11 @@ notification. The options defining the attribute can be provided in any order.
19
19
# --auth %ECF_AVISO_AUTH%
20
20
# --polling %ECF_AVISO_POLLING%
21
21
22
-
Notice that the :code:`--listener` option must be surrounded by single quotes,
23
-
and is composed as a single line `JSON`. The `JSON` must define two fields:
22
+
.. note::
23
+
24
+
The `listener` parameter is expected to be a valid single line JSON string, enclosed in single quotes.
25
+
26
+
The listener must define two fields (as per the `Aviso Listerner <https://pyaviso.readthedocs.io/en/latest/guide/define_my_listener.html>`_ definition):
24
27
25
28
- :code:`event`, specifies the type of Aviso event
26
29
- :code:`request`, specifies a dictionary with the parameters used to check for matches of Aviso notifications
@@ -34,12 +37,19 @@ The following are some examples:
0 commit comments