Skip to content

own the manifest processing #1402

@ffromani

Description

@ffromani

We mostly consume deployer for manifest processing. This was a good idea back in time, and enabled us a jump start. Over time, we had to focus on OCP-specific things which the deployer project is struggling to support.

Out of necessity, it seems it's time to move all the manifest processing in our own codebase, severing that dependency to the deployer package.

We may want to take the chance to remove all other deployer libs, or just keep consuming the most stable utility libraries.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions