We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No description provided.
The text was updated successfully, but these errors were encountered:
will it still support full paths or does this force the paths to be relative?
Sorry, something went wrong.
This is only about how to evaluate relative paths. Full/absolute paths would always be evaluated as such.
We could also offer options either from the command line and/or in the config file to tell it how to interpret relative paths.
Some thing like:
pathsRelativeTo: config|binary|env
where binary would be the ziti binary being run, config is the config file directory and env is whatever the default is.
A better approach would be to inject the config dir and the executable dir into the environment. Then we could use the env support.
So define zitiConfigDir and zitiBinDir. Then you could do things like:
zitiConfigDir
zitiBinDir
identity: cert: ${zitiConfigDir}/certs/server.cert
plorenz
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: