Skip to content

Rationale for requiring uid on DECLARATIVE_FRIENDLY resources #1580

@seanlafferty-ibm

Description

@seanlafferty-ibm

https://google.aip.dev/148#well-known-string-fields states about uids:

Declarative-friendly resources should include this field.

I am curious about this requirement (which is enforced in the linter) because a resource name should already be sufficient for declarative clients if we're following https://google.aip.dev/122, no?

each resource has a unique identifier that users use to reference that resource, and these names are what users should store as the canonical names for the resources.

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