Declarative Native App 매니페스트 참조¶

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

역할에 대한 자세한 내용은 :doc:`앱 역할<app-roles>`을 참조하세요.

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``(목록, [OneOfRequired]): 동적 테이블 및 :doc:`Apache Iceberg 테이블</user-guide/tables-iceberg>`을 포함할 수 있는 명명된 테이블의 목록입니다.

• ``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} 필드¶

명명된 각 표준 테이블, 동적 테이블 및 :doc:`Apache Iceberg 테이블</user-guide/tables-iceberg>`(목록, 필수 [OneOfRequired] )은 다음 이름 값 페어를 지원합니다.

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

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 예제¶

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.

sales_projections 및 **customer_analytics**의 두 가지 필수 데이터베이스도 노출됩니다. 이러한 데이터베이스는 공유 데이터베이스의 뷰에서 참조되지만 직접 공유되지는 않습니다.

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