Skip to content

"lookup_resource" macro should support different primary keys #847

@davepacheco

Description

@davepacheco

See #845. We want the new lookup API to support a few more cases:

  • where there's a composite primary key (e.g., for built-in roles and update artifacts) and "id" is usually not present
  • where there's no "name" column (e.g., for sleds, silo users)

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