Files
coredns.io/content/plugins/import.md
T
Miek Gieben 9d3c78f16f Sync notes from coredns
Make notes in coredns' repo to make it authoritative there.

Signed-off-by: Miek Gieben <miek@miek.nl>
2019-03-03 14:12:07 +00:00

77 lines
1.5 KiB
Markdown

+++
title = "import"
description = "*import* include files or reference snippets from a Corefile."
weight = 17
tags = [ "plugin", "import" ]
categories = [ "plugin" ]
date = "2019-03-03T14:11:50.603300"
+++
## Description
The *import* plugin can be used to include files into the main configuration. Another use it to
reference predefined snippets. Both can help to avoid some duplication.
This is a unique directive in that *import* can appear outside of a server block. In other words, it
can appear at the top of a Corefile where an address would normally be.
## Syntax
~~~
import PATTERN
~~~
* **PATTERN** is the file, glob pattern (`*`) or snippet to include. Its contents will replace
this line, as if that file's contents appeared here to begin with.
## Files
You can use *import* to include a file or files. This file's location is relative to the
Corefile's location. It is an error if a specific file cannot be found, but an empty glob pattern is
not an error.
## Snippets
You can define snippets to be reused later in your Corefile by defining a block with a single-token
label surrounded by parentheses:
~~~ corefile
(mysnippet) {
...
}
~~~
Then you can invoke the snippet with *import*:
~~~
import mysnippet
~~~
## Examples
Import a shared configuration:
~~~
. {
import config/common.conf
}
~~~
Where `config/common.conf` contains:
~~~
prometheus
errors
log
~~~
This imports files found in the zones directory:
~~~
import ../zones/*
~~~
## Also See
See corefile(5).