Skip to content

Add the ability to directly discrimate on name #2011

Description

@shawkins

For operators that have multiple dependent resources of the same type a common pattern is for those to be discriminated by name. While ResourceIDMatcherDiscriminator can account for this it does so by iterating over the list of resources. For an operator managing a fleet of resources this will eventually introduce unnecessary overhead. Ideally a built-in mechanism should be able to distinguish by name.

Similarly IndexDiscriminator could be promoted out of the samples.

Activity

  1. added this to the 4.5 milestone on Aug 10, 2023
  2. self-assigned this
    on Aug 10, 2023
  3. linked a pull request that will close this issuediscriminator improvements #2013on Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions