From 9389862d97b44f3b6a601390a61186d3519019f7 Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Mon, 12 Nov 2018 10:26:15 -0500 Subject: [PATCH] added faq entry on ansible_host + delegation (#48438) (cherry picked from commit 7ca6af396ed44e25ec8622c374e8f7d4f24f456b) --- docs/docsite/rst/reference_appendices/faq.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/docsite/rst/reference_appendices/faq.rst b/docs/docsite/rst/reference_appendices/faq.rst index 639bbc255e4..31bf620fdd1 100644 --- a/docs/docsite/rst/reference_appendices/faq.rst +++ b/docs/docsite/rst/reference_appendices/faq.rst @@ -596,6 +596,19 @@ Several reasons, in most cases it has to do with maintainability, there are tons In other cases there are technical issues, for example, for python wheels, our dependencies are not present so there is little to no gain. +.. _ansible_host_delegated: + +How do I get the original ansible_host when I delegate a task? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + +As the documentation states, connection variables are taken from the ``delegate_to`` host so ``ansible_host`` is overritten, +but you can still access the orignal via ``hostvars``:: + + oringal_host: "{{ hostvars[inventory_hostname]['ansible_host'] }}" + +This works for all overriden connection variables, like ``ansible_user``, ``ansible_port``, etc. + + .. _i_dont_see_my_question: I don't see my question here