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

Support yaml inheritance over variable files #11780

Closed
t2d opened this issue Jul 29, 2015 · 3 comments
Closed

Support yaml inheritance over variable files #11780

t2d opened this issue Jul 29, 2015 · 3 comments
Labels
affects_2.0 This issue/PR affects Ansible v2.0 affects_2.3 This issue/PR affects Ansible v2.3 feature This issue/PR relates to a feature request. needs_info This issue requires further information. Please answer any outstanding questions. needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly.

Comments

@t2d
Copy link

t2d commented Jul 29, 2015

Using yaml implicit inheritance in one variable file works fine and saves a lot of configuration lines.
Also ansible has its own concept of inheritance, which is quite verbose.
What does not work, is combining both.

I would like to define a parent element in group_vars/all.yml and override (parts of) it in host_vars/test.yml.
To make this happen, ansible would need to merge yaml files before handing them to the yaml parser.

@bcoca bcoca closed this as completed Jul 29, 2015
@t2d
Copy link
Author

t2d commented Jul 29, 2015

I edited the initial statement to underline that this is indeed a RFE. Please reopen.

@bcoca bcoca reopened this Jul 29, 2015
@jimi-c jimi-c removed the P5 label Dec 7, 2015
@ansibot ansibot added triage affects_2.0 This issue/PR affects Ansible v2.0 labels Sep 7, 2016
@ansibot ansibot added the affects_2.3 This issue/PR affects Ansible v2.3 label Dec 13, 2016
@bcoca bcoca removed the triage label Dec 16, 2016
@ansibot ansibot added needs_info This issue requires further information. Please answer any outstanding questions. needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly. labels Apr 4, 2017
@ansibot
Copy link
Contributor

ansibot commented Apr 4, 2017

@t2d Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

  • ansible version
  • component name

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

@t2d
Copy link
Author

t2d commented Apr 4, 2017

We handled our specific case with using the combine filter.

@t2d t2d closed this as completed Apr 4, 2017
@ansibot ansibot added feature This issue/PR relates to a feature request. and removed feature_idea labels Mar 2, 2018
@ansible ansible locked and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.0 This issue/PR affects Ansible v2.0 affects_2.3 This issue/PR affects Ansible v2.3 feature This issue/PR relates to a feature request. needs_info This issue requires further information. Please answer any outstanding questions. needs_template This issue/PR has an incomplete description. Please fill in the proposed template correctly.
Projects
None yet
Development

No branches or pull requests

4 participants