Skip to content

Allow one variable definition to define others, implicitly #67

Closed
@alechenninger

Description

For example, imagine a dynamic hierarchy like this:

hierarchy:
  sources:
    - common.yaml
    - environment/%{environment}.yaml
    - team/%{team}.yaml
    - team/%{team}/%{environment}.yaml
    - node/%{hostname}.yaml
  potentials:
    # snip...
    hostname:
      - myhost.prod.mycompany.com:
        environment: prod
        team: myteam

Then, if you defined a target by hostname=myhost.prod.mycompany.com, you would have a complete hierarchy, without having to manually define environment and team for that node too, which you already know statically in advance.

Additionally, the reverse is true. If you targeted environment=prod or team=myteam, you would know that host was a descendant.

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions