MDAA TS Docs
    Preparing search index...

    Glue-run configuration shared between a project's dataSourceDefaults and an individual data source. Any field specified on a data source entirely replaces the corresponding default (fields are not deep-merged); fields omitted on the data source fall back to the default, if any. There is no way to omit an inherited schedule other than setting the data source's own enableSetting to DISABLED, which disables the whole data source rather than just the schedule.

    interface DataSourceDefaultsProps {
        autoImportDataQualityResult?: boolean;
        enableSetting?: "ENABLED" | "DISABLED";
        filterExpressions?: DataSourceFilterExpressionProps[];
        publishOnImport?: boolean;
        recommendation?: DataSourceRecommendationProps;
        schedule?: DataSourceScheduleProps;
    }

    Hierarchy (View Summary)

    Index

    Properties

    autoImportDataQualityResult?: boolean

    Whether to automatically import AWS Glue Data Quality results as part of the data source run.

    AWS: AWS::DataZone::DataSource Configuration.GlueRunConfiguration.AutoImportDataQualityResult

    Validation: Optional; boolean

    true
    
    enableSetting?: "ENABLED" | "DISABLED"

    Whether the data source is enabled to run.

    AWS: AWS::DataZone::DataSource EnableSetting

    Validation: Optional; 'ENABLED' | 'DISABLED'

    ENABLED (DataZone default)
    
    filterExpressions?: DataSourceFilterExpressionProps[]

    Filter expressions limiting which tables in the Glue database are imported. When omitted, every table in the database is imported.

    Use cases: Importing a subset of tables from a large shared database

    AWS: AWS::DataZone::DataSource Configuration.GlueRunConfiguration.RelationalFilterConfigurations[].FilterExpressions

    Validation: Optional; array of DataSourceFilterExpressionProps

    - every table in the database is imported
    
    publishOnImport?: boolean

    Whether assets imported by the data source are automatically published to the project's catalog. When false, imported assets remain in the project inventory and must be published by hand.

    Use cases: Publish-and-subscribe data mesh models; Automated asset catalog population

    AWS: AWS::DataZone::DataSource PublishOnImport

    Validation: Optional; boolean

    false (DataZone default; assets are not auto-published)
    

    Business name generation recommendation configuration for assets this data source imports.

    AWS: AWS::DataZone::DataSource Recommendation (AWS::DataZone::DataSource RecommendationConfiguration)

    Validation: Optional; DataSourceRecommendationProps

    - business name generation is not enabled
    

    Schedule on which the data source runs automatically. When omitted, the data source never runs on its own and must be run manually or via another trigger.

    Use cases: Automated, recurring metadata import

    AWS: AWS::DataZone::DataSource Schedule (AWS::DataZone::DataSource ScheduleConfiguration)

    Validation: Optional; DataSourceScheduleProps

    - data source does not run on a schedule