Add documentation for json schema usage to validate config in the FAQ
Co-authored-by: Kevin Pollet <pollet.kevin@gmail.com>
This commit is contained in:
parent
d06573de6c
commit
1c9a7b8c61
1 changed files with 24 additions and 0 deletions
|
@ -157,3 +157,27 @@ By default, the following headers are automatically added when proxying requests
|
||||||
|
|
||||||
For more details,
|
For more details,
|
||||||
please check out the [forwarded header](../routing/entrypoints.md#forwarded-headers) documentation.
|
please check out the [forwarded header](../routing/entrypoints.md#forwarded-headers) documentation.
|
||||||
|
|
||||||
|
## What does the "field not found" error mean?
|
||||||
|
|
||||||
|
```shell
|
||||||
|
error: field not found, node: -badField-
|
||||||
|
```
|
||||||
|
|
||||||
|
The "field not found" error occurs, when an unknown property is encountered in the dynamic or static configuration.
|
||||||
|
|
||||||
|
One easy way to check whether a configuration file is well-formed, is to validate it with:
|
||||||
|
|
||||||
|
- [JSON Schema of the static configuration](https://json.schemastore.org/traefik-v2.json)
|
||||||
|
- [JSON Schema of the dynamic configuration](https://json.schemastore.org/traefik-v2-file-provider.json)
|
||||||
|
|
||||||
|
## Why are some resources (routers, middlewares, services...) not created/applied?
|
||||||
|
|
||||||
|
As a common tip, if a resource is dropped/not created by Traefik after the dynamic configuration was evaluated,
|
||||||
|
one should look for an error in the logs.
|
||||||
|
|
||||||
|
If found, the error obviously confirms that something went wrong while creating the resource,
|
||||||
|
and the message should help in figuring out the mistake(s) in the configuration, and how to fix it.
|
||||||
|
|
||||||
|
When using the file provider,
|
||||||
|
one easy way to check if the dynamic configuration is well-formed is to validate it with the [JSON Schema of the dynamic configuration](https://json.schemastore.org/traefik-v2-file-provider.json).
|
||||||
|
|
Loading…
Reference in a new issue