Skip to content

Broader filtering solution needed for using database.yml #575

Description

@ianballou

src/vars/database.yml (https://github.com/ianballou/foremanctl/blob/master/src/vars/database.yml) defines information about databases. The recent addition of backup in foremanctl exposed that IoP database information was being used to create backup files even when the IoP feature was not enabled.

We discussed if backup/restore should conditionally load bits of database.yml based on what features are available, but I think this feature should be more broad. Each playbook should not be responsible for its own correct parsing of database.yml.

One idea is to split the database file for each feature. Then the files could be conditionally loaded based on what features are enabled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions