Skip to content
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

remote_tmp should be configurable within group_vars and host_vars #29019

Closed
tbar74235 opened this issue Sep 5, 2017 · 5 comments
Closed

remote_tmp should be configurable within group_vars and host_vars #29019

tbar74235 opened this issue Sep 5, 2017 · 5 comments
Assignees
Labels
affects_2.2 This issue/PR affects Ansible v2.2 feature This issue/PR relates to a feature request. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Milestone

Comments

@tbar74235
Copy link

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

remote_tmp var in ansible.cfg

ANSIBLE VERSION
ansible 2.2.2.0
  config file = /opt/jboss/ansible/ansible.cfg
  configured module search path = Default w/o overrides
CONFIGURATION

remote_tmp in ansible.cfg

OS / ENVIRONMENT

N/A

SUMMARY

The problem is that I am only able to configure the remote_tmp var within ansible.cfg.
But each host I like to administrate with ansible could have another path I wish to write the ansible tmp files to.

STEPS TO REPRODUCE

I should be able to configure the remote_tmp var within group_vars for example. Currently this will be ignored. Only the value of remote_tmp within ansible.cfg will be taken.

EXPECTED RESULTS

I would expect that if I would configure a remote_tmp property within group_vars or host_vars the remote_tmp property of ansible.cfg will be overwritten. So could define a special remote_tmp path for each host or host groups for example.

ACTUAL RESULTS

Currently only the remote_tmp property of ansible.cfg is the only option to change the remote_tmp path which every host you define within your ansible configuration must have.

@bcoca bcoca added this to the 2.5.0 milestone Sep 5, 2017
@bcoca
Copy link
Member

bcoca commented Sep 5, 2017

We already have plans to add this in the next version.

@tbar74235
Copy link
Author

Would you specify the version which will contain this feature?

@bcoca bcoca self-assigned this Sep 5, 2017
@bcoca
Copy link
Member

bcoca commented Sep 5, 2017

it is on the 2.5 roadmap draft

@ansibot ansibot added affects_2.2 This issue/PR affects Ansible v2.2 feature_idea needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Sep 5, 2017
@samdoran samdoran removed the needs_triage Needs a first human triage before being processed. label Sep 5, 2017
@alikins
Copy link
Contributor

alikins commented Oct 4, 2017

See also #31022

@bcoca
Copy link
Member

bcoca commented Feb 15, 2018

fixed via #31677

@bcoca bcoca closed this as completed Feb 15, 2018
@ansibot ansibot added feature This issue/PR relates to a feature request. and removed feature_idea labels Mar 3, 2018
@ansible ansible locked and limited conversation to collaborators Apr 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.2 This issue/PR affects Ansible v2.2 feature This issue/PR relates to a feature request. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

No branches or pull requests

5 participants