Declarative Native App manifest reference¶

application_content.notebooks.{named notebook} 字段¶

每个命名笔记本都支持以下名称值对：

• ``main_file``（字符串，必填）交互式 Python 笔记本 (.ipynb) 文件的名称。

• ``comment``（字符串，可选）：用于描述笔记本的注释。

• ``runtime_environment_version``（字符串，可选）： 为笔记本执行上下文指定特定的 :ref:`运行时环境版本 <label-notebook_runtime_descriptions>`（如果适用于平台）。

• 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 示例¶

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

有关角色的详细信息，请参阅 应用程序角色。

shared_content.databases.{named database} 字段¶

每个命名数据库都支持以下名称值对：

• ``schemas``（列表，必填）： 数据库中的架构列表。

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.

schemas.{named schema} 字段¶

每个命名架构都支持以下名称值对：

• tables (list, [OneOfRequired]): A list of named tables, which can include dynamic tables.

• ``views``（列表，[OneOfRequired]）：命名视图的列表。

• 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.

tables.{named table} 字段¶

Each named standard or dynamic table (List, required [OneOfRequired] ) supports the following name value pair:

• 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.

views.{named view} 字段¶

每个命名视图（列表，必填 [OneOfRequired]）：支持以下名称值对：

• 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.

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.

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.

shared_content 示例¶

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.

Two required databases are also exposed: sales_projections and customer_analytics. These databases can be referenced by views in the shared databases, but are not shared directly.

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