Skip to content

Structuing assets #142

@fabiand

Description

@fabiand

I was wondering how the assets should be structured.
Generally I see two ways

  • topic driven
  • operator driven

topic driven would require to have configs in different places, but this is not possible with many operators,
thus I tend to think that we want to have one dir per operator, maybe we even require the dir to be named according to the

  • namespace
  • or operator name
    ?

I'm referring to the dirs in https://github.com/openshift-virtualization/virt-platform-autopilot/tree/main/assets/active

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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