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
Please note that within the transport schema, the following keywords are reserved words:
243
-
244
-
#### Usable within the schema
245
-
246
-
The following keywords are encouraged within the Transport schema:
247
-
248
-
*`uri` - Use when you need to specify a specific URL to connect to. All of the following keys will be computed from the `uri` if possible. In the future more url parts may be computed from the URI as well.
249
-
*`host` - Use to specify and IP or address to connect to.
250
-
*`protocol` - Use to specify which protocol the transport should use for example `http`, `https`, `ssh` or `tcp`
251
-
*`user` - The user the transport should connect as.
252
-
*`port` - The port the transport should connect to.
253
-
254
-
#### Non-Usable within the schema
255
-
256
-
The following keywords are keywords that must not be used by the transport schema:
257
-
258
-
*`name` - transports should use `uri` instead of name.
259
-
*`path` - reserved as a uri part
260
-
*`query` - reserved as a uri part
261
-
*`run-on` - This is used by bolt to determine which target to proxy to. Transports should not rely on this key.
262
-
*`remote-transport` - This is used to determine which transport to load. It should always be the transport class name "declassified".
263
-
*`remote-*` Any key starting with `remote-` is reserved for future use.
264
-
*`implementations`: reserved by bolt
265
-
266
-
Note: Currently bolt inventory requires that a name be set for every target and always uses that name as the URI. This means there is no way to specify `host` separately from the host section of the `name` when parsed as a URI.
242
+
To align with [Bolt's inventory file](https://puppet.com/docs/bolt/latest/inventory_file.html), a transport schema prefers the following keywords (when relevant):
243
+
244
+
*`uri`: use when you need to specify a specific URL to connect to. Bolt will compute the following keys from the `uri` when possible. In the future more url parts may be computed from the URI.
245
+
*`protocol`: use to specify which protocol the transport should use for example `http`, `https`, `ssh` or `tcp`.
246
+
*`host`: use to specify an IP or address to connect to.
247
+
*`port`: the port the transport should connect to.
248
+
*`user`: the user the transport should connect as.
249
+
*`password`: the password for the specified user.
250
+
251
+
Do not use the following keywords when writing a schema:
252
+
253
+
*`implementations`: reserved by Bolt.
254
+
*`name`: transports should use `uri` instead of name.
255
+
*`path`: reserved as a uri part.
256
+
*`query`: reserved as a uri part.
257
+
*`remote-*`: any key starting with `remote-` is reserved for future use.
258
+
*`remote-transport`: determines which transport to load. It is always the transport class named "declassified".
259
+
*`run-on`: Bolt uses this keyword to determine which target to proxy to. Transports should not rely on this key.
260
+
261
+
> Note: Bolt inventory requires you to set a name for every target and always use it for the URI. This means that there is no way to specify `host` separately from the host section of the `name` when parsed as a URI.
267
262
268
263
After the device class, transport class and transport schema have been implemented, `puppet device` will be able to use the new provider, and supply it (through the device class) with the URL specified in the [`device.conf`](https://puppet.com/docs/puppet/5.3/config_file_device.html).
0 commit comments