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: doc/installationguide.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -227,7 +227,7 @@ used for the same purpose. For instance:
227
227
-**singleConfigurationMode**: enables the Single Configuration mode for backwards compatibility (see description in
228
228
the Overview). Default to false.
229
229
-**timestamp**: if this flag is activated:
230
-
- For NGSIv1/NGSIv2, the IoT Agent will add a `TimeInstant` metadata attribute to all the attributes updated from device information.
230
+
- For NGSIv1/NGSIv2, the IoT Agent will add a `TimeInstant` metadata attribute to all the attributes updated from device information.
231
231
This flag is overwritten by `timestamp` flag in group or device
232
232
- With NGSI-LD, the standard `observedAt` property-of-a-property is created instead.
233
233
-**defaultResource**: default string to use as resource for the registration of new Configurations (if no resource is
@@ -255,6 +255,11 @@ used for the same purpose. For instance:
255
255
Note that for backwards compatibility with NGSI v2, the `fiware-servicepath` header is already used as alternative if the `NGSILD-Path` header is not supplied. Note that NGSILD-Path has not yet been included in the NGSI-LD standard (it has been proposed for the next update of the standard, but the final decision has yet been confirmed), take into account it could change
256
256
-**explicitAttrs**: if this flag is activated, only provisioned attributes will be processed to Context Broker.
257
257
This flag is overwritten by `explicitAttrs` flag in group or device provision.
258
+
-**relaxTemplateValidation**: if this flag is activated, `objectId` attributes for incoming devices are not validated,
259
+
and may exceptionally include characters (such as semi-colons) which are
260
+
[forbidden](https://fiware-orion.readthedocs.io/en/master/user/forbidden_characters/index.html) according to the NGSI
261
+
specification. When provisioning devices, it is necessary that the developer provides valid `objectId`-`name` mappings
262
+
whenever relaxed mode is used, to prevent the consumption of forbidden characters.
258
263
259
264
### Configuration using environment variables
260
265
@@ -264,7 +269,7 @@ with container-based technologies, like Docker, Heroku, etc...
264
269
The following table shows the accepted environment variables, as well as the configuration parameter the variable
- If you need to pass more than one JSON-LD context, you can define the IOTA_JSON_LD_CONTEXT environment variable as a comma separated list of contexts (e.g. `'http://context1.json-ld,http://context2.json-ld'`)
0 commit comments