Target tenant resources
These tables show the resources that can be included in the global packages:
Data Catalog:
| Resource | Category | Description | Read-only package | Editable package |
|---|---|---|---|---|
| Object Schemas | Content | An object schema contains the metadata describing the contents of a data object. | User cannot edit, export, or delete a GPN resource. |
These two instances are created during the deployment:
User can edit the live instance in the application. User can export and re-import the live instance for the purpose of updating the instance's content. User can't edit, export, or delete the template instance. User can't delete or include either instance in a local package. |
| Data Lake Views | Content | A Data Lake view schema contains metadata that defines the view and specifies the query that is used to create the view. | User can't modify or drop the view. |
These two view instances are created during the deployment:
To update the view schema, open the reference version, copy the query from the Query tab, and use it to modify the view in Compass. User can't drop the view or include either instance in a local package. |
| Schema Extensions | Content | Schema extensions allow for customizations to be made on Standard BODs. |
User can't edit, export, or delete a schema file that is a GPN resource. User can't edit or delete a schema extension with a GPN schema file. User can't add a new schema extension to a GPN schema file. |
Not supported. Schema extensions can't be included in editable global packages. |
| Locale Selections | Configuration | Locale selections allow for localized data to be queried by the Compass Query Platform. | Locale selections are editable even in read-only packages. | Editable. Only a single instance is deployed. Content is overwritten at each package deployment. |
Pipelines:
| Resource | Category | Description | Read-only package | Editable package |
|---|---|---|---|---|
| Destinations | Content | Destinations are used to establish and manage the connectivity to the target systems in which data is streamed with Stream Pipelines. |
User cannot delete a GPN resource. User can edit only connection details and credentials in a GPN resource. User can export a GPN resource. |
These two instances are created during the deployment:
User can edit the live instance in the application. User can't export or delete the live instance. User can't edit, export, or delete the template instance. User can't include either instance in a local package. |
| Stream Pipelines | Content | Stream pipelines are models that define continuous data flows through Data Fabric to designated destinations. Stream pipelines ensure immediate data delivery. | User cannot edit, export, or delete a GPN resource. |
These two instances are created during the deployment:
User can edit the live instance in the application. User can't delete the live instance. User can't edit or delete the template instance. User can't include either instance in a local package. |