Structuring Configuration Documents for Import

The Configuration Importer runs from a base directory and looks for configuration documents in a subdirectory named "config". Other supporting files and directories can be added to the base directory and referenced from the configuration documents. For more details on referencing external files from within configuration documents, see Object References.

The following is an example directory structure:

/import/

├── config/

| ├── configuration-document-1.yaml

| ├── configuration-document-2.yaml

| ...

├── data/

| ├── my-rule.zts

| └── catalog.json

├── secrets/

| └── db-password

└── tls/

└── example-service/

├── tls.key

└── tls.crt

 

When the Configuration Importer is fully managing the configuration, changes to any files under the base directory result in the Traffic Manager's configuration being updated.

The base directory must be visible in the file system of the Traffic Manager. The Configuration Importer expects that the contents of the directory are populated from an external system; for example, being mounted or mapped into the Traffic Manager's filesystem from a persistent volume, or pulled from an external repository.