A Glean Resource Name or GRN is a way to reference Glean resources in a stable way. As a resource is changed, renamed, moved between collections, etc. its GRN will always remain the same.
A GRN is comprised of three components: type, id, and alias, separated by
typeidentifies the resource type
palette: color palette
sv: saved exploration
idis an globally unique identifier first assigned when the resource is created. The ID appears in the URL bar when viewing a resource.
aliasis an optional unique identifier set by the user in the resource's DataOps config.
Not all 3 components are necessary to specify a GRN. The
alias can be omitted as long as an
id is present:
and, likewise, the
id can be omitted as long as an
alias is specified (note the double
The following are all valid GRNs:
# some GRNs have longer IDs:
GRNs are case sensitive.
All resources can be specified with the special
grn property to link a DataOps
config to an existing resource. This allows you to move a resource created in
the Glean web app into DataOps, without recreating it.
Anywhere you specify a filepath in a DataOps config, you may instead specify a GRN. This allows you to reference resources independently of how you structure your files.
When referencing models imported by the dbt integration, the standard GRN format is valid. It is also possible to reference dbt models using the unique identifier of the dbt node representing the model: