FAQ

1. What is the syntax for custom configuration templates?

Template must be as per Apache Velocity 1.7 template rules and syntax. For more information, see https://velocity.apache.org/engine/1.7/user-guide.html.

2. Are there restrictions on destination directories?

Yes, certain directories are non-writable by some processes. Recommended locations are /etc or /var and their sub directories. Do not use /opt/mashery and sub directories as a destination since they are a read-only resource locations.

3. What happens if destination directory not exist?

The container agent will attempt to create the required directories, provided it has the required permissions. Check container agent logs for IOExceptions.

4. Can I provide any names for the templates?

Yes. the templates can have any name but the extension has to be .template. For example the template for adapter.properties will be named as adapter.properties.template.

5. Is the specification file mandatory?

Yes. If there is no specification file, the container agent will ignore the resources when merging configuration values and generating configurations.

6. Can I change custom configuration properties post cluster creation?

Yes. Using the clustermanager cli clustermanager set the configuration command. The container agent will regenerate configurations from the templates and new properties.