You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 21, 2020. It is now read-only.
First thanks a million for creating this tutorial. I am using it to learn ansible. Quick note is that in the /setup/main.yml file where you are copying the pg_hba.conf file you have a harcoded path to the file. I wonder if there is a way to query for the version of postress to put in the path as a variable? For now I am updating to 9.3 locally. Thanks.
You could do this with the templates module in Ansible, I was trying to keep things as simple as possible when I wrote this. However, I think you're probably correct and using a template would be better practice and good to teach people. As with #2, feel free to submit a pull request, but otherwise I'll take a look when I get home.
I'm going to have to take a proper look at this one at a later date; simply didn't have time today. However, I think this is possible by parsing the shell output with Regex as explained in the Ansible Variables documentation.
However, should this prove not to be possible the next best thing would be to to expose the version number as a variable, and then install the specified version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Daniel,
First thanks a million for creating this tutorial. I am using it to learn ansible. Quick note is that in the /setup/main.yml file where you are copying the pg_hba.conf file you have a harcoded path to the file. I wonder if there is a way to query for the version of postress to put in the path as a variable? For now I am updating to 9.3 locally. Thanks.
[email protected]
The text was updated successfully, but these errors were encountered: