From 9ff2a8d44dcf301e517a4c7a8a2754201d1e30c0 Mon Sep 17 00:00:00 2001 From: Esguerra Date: Sat, 13 Oct 2018 04:53:33 +0800 Subject: [PATCH] first change --- docs/additional-features/context-data.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/additional-features/context-data.md b/docs/additional-features/context-data.md index 465b4d2dc..d510322ea 100644 --- a/docs/additional-features/context-data.md +++ b/docs/additional-features/context-data.md @@ -3,3 +3,6 @@ Sometimes it is desirable to associate arbitrary data with a group of devices to aid in their configuration. For example, you might want to associate a set of syslog servers for all devices at a particular site. Context data enables the association of arbitrary data to devices and virtual machines grouped by region, site, role, platform, and/or tenant. Context data is arranged hierarchically, so that data with a higher weight can be entered to override more general lower-weight data. Multiple instances of data are automatically merged by NetBox to present a single dictionary for each object. Devices and Virtual Machines may also have a local config context defined. This local context will always overwrite the rendered config context objects for the Device/VM. This is useful in situations were the device requires a one-off value different from the rest of the environment. + + +Test change \ No newline at end of file