Referenz zum Declarative Native App-Manifest¶

Feld application_content.notebooks.{named notebook}¶

Jedes benannte Notizbuch unterstützt die folgenden Name/Wert-Paare:

• main_file (Zeichenfolge, erforderlich) ist der Name der interaktiven Python-Notizbuchdatei (.ipynb).

• comment (Zeichenfolge, optional): Ein Kommentar, der das Notizbuch beschreibt.

• runtime_environment_version (Zeichenfolge, optional): Gibt eine bestimmte Version der Laufzeitumgebung für den Ausführungskontext des Notizbuchs an, falls innerhalb der Plattform anwendbar.

• roles (list, optional): A list of app roles that can grant access to the notebook, for example, [sales,marketing]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field.

application_content:
    notebooks:
        - salesbook:
              roles: [sales, marketing]
              main_file: NOTEBOOK1.ipynb
              comment: Notebook1: Sales and marketing notebook
              runtime_environment_version: stable

roles:
  - sales:
  - marketing:

roles-Beispiel¶

roles:
  - sales:
  - marketing:

application_content:
  notebooks:
    - salesbook:
        roles: [sales, marketing]
        main_file: NOTEBOOK1.ipynb
        comment: Sales and marketing notebook

shared_content:
  databases:
    - sales:
        schemas:
          - orders:
              roles: [sales, marketing]
              tables:
                - january_2025:        # App owners/assignees only
                - february_2025:
                    roles: [sales]     # Accessible to sales only
                - march_2025:
                    roles: [marketing] # Accessible to marketing only
    - customer_info:
        schemas:
          - customer_contact:
              roles: [customer_support]
              views:
                - customer_address:
                    roles: [customer_support] # Accessible to customer_support
                - customer_details:
                    roles: []                 # App owners/assignees only

Weitere Informationen zu Rollen finden Sie unter App-Rollen

Feld shared_content.databases.{named database}¶

Jede benannte Datenbank unterstützt die folgenden Name/Wert-Paare:

• schemas (Liste, erforderlich): Eine Liste der Schemas innerhalb der Datenbank.

shared_content.required_databases.{named database} field¶

The required_databases field (list, optional) defines a list of databases that are dependencies of the shared databases. These databases are referenced by views in the shared databases, but are not shared directly. When your application shares data from multiple databases, you must explicitly list all additional databases that are referenced by objects in your shared content under the required_databases field. This ensures that the application can be deployed successfully in other regions where these databases may not exist by default. Including a database in the required_databases field is similar to referencing a database using the REFERENCE_USAGE privilege in traditional Secure Data Sharing. For information about the REFERENCE_USAGE privilege and how dependent databases are shared in traditional data sharing, see Share data from multiple databases.

Feld schemas.{named schema}¶

Jedes benannte Schema unterstützt die folgenden Name/Wert-Paare:

• tables (Liste, [OneOfRequired]): Eine Liste von benannten Tabellen, die dynamische Tabellen und Apache Iceberg-Tabellen enthalten können.

• views (Liste, [OneOfRequired]): Eine Liste von benannten Ansichten.

• semantic_views (list, [OneOfRequired]): A list of named semantic views.

• functions (list, [OneOfRequired]): A list of named user-defined functions (UDFs).

• procedures (list, [OneOfRequired]): A list of named stored procedures.

• roles (list, optional): A list of app roles that the objects in the schema can use, for example, [sales,marketing]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field.

Feld tables.{named table}¶

Jede benannte Standardtabelle (dynamische Tabelle (Liste, erforderlich [OneOfRequired] )) unterstützt das folgende Name-Wert-Paar:

• roles (list, optional): A list of app roles that can access the table; for example, [sales]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field and included in the {named schema}.roles field.

Feld views.{named view}¶

Jede benannte Ansicht (Liste, erforderlich [OneOfRequired] ): unterstützt das folgende Name/Wert-Paar:

• roles (list, optional): A list of app roles that can access the view; for example, [marketing]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field and included in the {named schema}.roles field.

semantic_views.{named semantic view} field¶

Each named semantic view (List, required [OneOfRequired] ): supports the following name value pair:

• roles (list, optional): A list of app roles that can access the semantic view; for example, [sales]. Note that, when sharing a semantic view, its referenced tables or views must be shared as well. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field and included in the {named schema}.roles field.

functions.{named function} field¶

Each named function (List, required [OneOfRequired] ): supports the following name value pair:

• roles (list, optional): A list of app roles that can access the function; for example, [analyst]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field and included in the {named schema}.roles field.

procedures.{named procedure} field¶

Each named stored procedure (List, required [OneOfRequired] ): supports the following name value pair:

• roles (list, optional): A list of app roles that can access the procedure; for example, [analyst]. When this field is empty ([]) or omitted, then only app owners and roles with granted IMPORTED PRIVILEGES receive access. The included roles must be defined in the top-level roles field and included in the {named schema}.roles field.

shared_content-Beispiel¶

In this example, two databases are exposed: sales and customer_info. Within these databases the orders.[january_2025|february_2025] tables are exposed as well as the customer_contact.customer_address view.

Zwei erforderliche Datenbanken sind ebenfalls verfügbar: sales_projections und customer_analytics. Diese Datenbanken können über Ansichten in den freigegebenen Datenbanken referenziert werden, werden aber nicht direkt freigegeben.

roles:
  - sales:
  - marketing:

shared_content:
  required_databases:
    sales_projections
    customer_analytics
  databases:
    - sales:
        schemas:
          - orders:
              roles: [sales, marketing]
              tables:
                - january_2025:        # App owners/assignees only
                - february_2025:
                    roles: [sales]     # Accessible to sales only
                - march_2025:
                    roles: [marketing] # Accessible to marketing only
    - customer_info:
        schemas:
          - customer_contact:
              roles: [customer_support]
              views:
                - customer_address:
                    roles: [customer_support] # Accessible to customer_support
                - customer_details:
                    roles: []                 # App owners/assignees only