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
There's Perms option to change template permissions, why wouldn't there be 'chown' capability as well ?
There's lots of use cases where you would want the destination file to be owned by someone other than the user running consul-template.
You could run multiple instances for each user, sure, but that's kinda lame.
Looking at the code this should be fairly simple. Should I give it a go ?
The text was updated successfully, but these errors were encountered:
Unfortunately it's not that easy.
Duplicate of #494 and #461. Please see the comments on those tickets for more information.
Sorry, something went wrong.
No branches or pull requests
There's Perms option to change template permissions, why wouldn't there be 'chown' capability as well ?
There's lots of use cases where you would want the destination file to be owned by someone other than the user running consul-template.
You could run multiple instances for each user, sure, but that's kinda lame.
Looking at the code this should be fairly simple. Should I give it a go ?
The text was updated successfully, but these errors were encountered: