Use ip's for production hosts when creating dump and syncing #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use production host from the inventory with a different hostname
<hostname>.prod
when creating the dump and syncing to avoid dns/Ansibleissues where the dump would be created on the target machine instead of the
production machine. This requires that the production ip's are specified
in the inventory under the .prod hostname with
ansible_host
and possiblythe user with
ansible_user
if running against Vagrant VM where the used userdoesn't match the one used on the production machine.
This should be merged at around the same time with the corresponding file sync change and possibly inventory changes.