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
Hello, thanks for role (and promtail one)
Wanted to ask if it's possible to change variable prefix to loki_canary_*, which will be also more consistent with role name (loki-canary).
The text was updated successfully, but these errors were encountered:
Thank you for the feedback - is there any specific problem you are currently encountering with the variable names?
As the variable names are already quite long, I would then rather prefer to use the "ansible-openshift" convention of using the first two letters of the role name for the variable: https://github.com/openshift/openshift-ansible/blob/master/docs/style_guide.adoc#ansible-role-variables
This would result in lc_* variables - however to me this seems a bit more confusing and might more easily overlap with other roles
lc_*
Do you have another community document where best-practices regarding variable names are documented?
Sorry, something went wrong.
Sorry for late reply
is there any specific problem you are currently encountering with the variable names?
I happen to have canary role myself, internal app. I know, my problems, but still.
Better than canary_ for sure, but probably can be confused with internal linux LC_* (locale) variables.
I do not know about any guidelines for variable names.
No branches or pull requests
Hello, thanks for role (and promtail one)
Wanted to ask if it's possible to change variable prefix to loki_canary_*, which will be also more consistent with role name (loki-canary).
The text was updated successfully, but these errors were encountered: