|
3 | 3 |
|
4 | 4 | .. important:: |
5 | 5 |
|
6 | | - The following example is more complex code than the other examples, |
| 6 | + The following example is more complex code than the general examples, |
7 | 7 | generating data and interacting with Orchestrator. Using and |
8 | 8 | modifying these examples requires a greater understanding of python |
9 | 9 | functions, handling variables, and additional tools such as Jinja. |
10 | 10 |
|
11 | 11 |
|
| 12 | +.. note:: |
| 13 | + |
| 14 | + The code referenced in this document and all published examples |
| 15 | + with pyedgeconnect are available from the GitHub repository within the |
| 16 | + `examples <https://https://github.com/SPOpenSource/edgeconnect-python/tree/main/examples>`_ |
| 17 | + folder |
| 18 | + |
12 | 19 | Generate EdgeConnect Preconfig |
13 | 20 | ------------------------------ |
14 | 21 |
|
@@ -154,17 +161,19 @@ Additional availble runtime arguments are as follows: |
154 | 161 | - ``-o`` or ``--orch`` |
155 | 162 | - Type: String |
156 | 163 | - Desc: Specify the Orchestrator IP or FQDN |
157 | | - - Example values: ``10.100.1.90`` or ``orchestrator.<company>.com`` |
| 164 | + - Example values: ``192.0.2.100`` or ``orchestrator.<company>.com`` |
158 | 165 | - Default value: ``None`` |
159 | 166 | - ``-u`` or ``--upload`` |
160 | 167 | - Type: Boolean |
161 | | - - Desc: Upload the rendered YAML preconfig to Orchestrator |
162 | | - - Accepted values: ``True`` or ``False`` |
| 168 | + - Desc: Upload the rendered YAML preconfig to Orchestrator. |
| 169 | + Including the ``-u`` will translate to ``True``, no option will |
| 170 | + default to ``False`` |
163 | 171 | - Default value: ``False`` |
164 | 172 | - ``-aa`` or ``--autoapply`` |
165 | 173 | - Type: Boolean |
166 | | - - Desc: Auto-apply the YAML preconfig on Orchestrator to a discovered appliance |
167 | | - - Accepted values: ``True`` or ``False`` |
| 174 | + - Desc: Auto-apply the YAML preconfig on Orchestrator to a |
| 175 | + discovered appliance. Including the ``-aa`` will translate to |
| 176 | + ``True``, no option will default to ``False`` |
168 | 177 | - Default value: ``False`` |
169 | 178 | - ``-j`` or ``--jinja`` |
170 | 179 | - Type: String |
@@ -209,7 +218,8 @@ Orchestrator API calls |
209 | 218 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ |
210 | 219 |
|
211 | 220 | The two API calls to Orchestrator (outside of authentication) are |
212 | | -``validate_preconfig`` and ``create_preconfig``. |
| 221 | +:func:`pyedgeconnect.Orchestrator.validate_preconfig` and |
| 222 | +:func:`pyedgeconnect.Orchestrator.create_preconfig`. |
213 | 223 |
|
214 | 224 | The ``validate_preconfig`` function sends the preconfig YAML text to |
215 | 225 | Orchestrator and will either return a success (HTTP 200 OK) or if |
|
0 commit comments