-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
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
Remove update_cache or make it optional #63
Comments
If we are not updating the cache per default, I fear that the installation might fail for people who are not aware, that they need to have updated the cache themselves first. In my mind this leads to a bad default experience with ansible roles. I'd be open for a suggestion how to best handle this. Do you know of any convention (i.e. a specific variable name) that we could use to conditionally enable/disable the behaviour ? |
I see.
I'm unaware of any convention, sorry. Making it a variable, that is default true, so we could opt-out of the behaviour would be great. |
Sounds like a good compromise to me - happy to get a PR and would gladly build a new release 👍 |
In the step that ensure unzip is installed to the managed hosts you are setting
update_cache: yes
.ansible-role-promtail/tasks/install.yml
Lines 2 to 6 in dd3c702
Would it be a reasonable ask to let administrators handle
update_cache
themselves, soapt-get update
is only executed once per run, instead of possibly multiple times, due to this role forcing it?The text was updated successfully, but these errors were encountered: