Skip to content

common/ocp_resources should not hard code handling of all files to be processed #961

@RobertKrawitz

Description

@RobertKrawitz

Is your feature request related to a problem? Please describe.
Currently common/ocp_resources has inline code to handle each resource file that needs to be processed. This should be generalized. At present, whenever a new resource file is added, corresponding code has to be added to handle it. That's clumsy and error-prone.

Describe the solution you'd like
nn-resource files should be Python code imported and run on the fly that does everything the inline code does; the dispatcher simply loads each file in lexical sequence. This is similar to how other systems files (e. g. /etc/NetworkManager/dispatcher.d) handle this.

Describe alternatives you've considered
None

Additional context
This is cleanup, not really either a bug or a feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions