NAME
    gcloud alpha storage insights dataset-configs create - create a new dataset
        config for Insights

SYNOPSIS
    gcloud alpha storage insights dataset-configs create DATASET_CONFIG_NAME
        --location=LOCATION --organization=SOURCE_ORG_NUMBER
        --retention-period-days=RETENTION_DAYS
        (--source-projects=[SOURCE_PROJECT_NUMBERS,...]
          | --source-projects-file=SOURCE_PROJECT_NUMBERS_IN_FILE)
        [--auto-add-new-buckets] [--description=DESCRIPTION]
        [--identity=IDENTITY_TYPE; default="IDENTITY_TYPE_PER_CONFIG"]
        [--exclude-bucket-names=[BUCKETS_NAMES,...]
          --exclude-bucket-prefix-regexes=[BUCKETS_REGEXES,...]
          | --include-bucket-names=[BUCKETS_NAMES,...]
          --include-bucket-prefix-regexes=[BUCKETS_REGEXES,...]]
        [--exclude-source-locations=[LIST_OF_SOURCE_LOCATIONS,...]
          | --include-source-locations=[LIST_OF_SOURCE_LOCATIONS,...]]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (ALPHA) Create a new dataset config for Insights.

EXAMPLES
    To create a dataset config with config name as "my-config" in location
    "us-central1" and project numbers "123456" and "456789" belonging to
    organization number "54321":

        $ gcloud alpha storage insights dataset-configs create my-config \
           --location=us-central1 --source-projects=123456,456789 \
           --organization=54321 --retention-period-days=1

    To create a dataset config that automatically adds new buckets into config:

        $ gcloud alpha storage insights dataset-configs create my-config \
           --location=us-central1 --source-projects=123456,456789 \
           --organization=54321 --auto-add-new-buckets \
           --retention-period-days=1

POSITIONAL ARGUMENTS
     DATASET_CONFIG_NAME
        Provide human readable config name.

REQUIRED FLAGS
     --location=LOCATION
        Provide location of the dataset config.

     --organization=SOURCE_ORG_NUMBER
        Provide the source organization number.

     --retention-period-days=RETENTION_DAYS
        Provide retention period for the config.

     List of source project numbers or the file containing list of project
     numbers.

     Exactly one of these must be specified:

       --source-projects=[SOURCE_PROJECT_NUMBERS,...]
          List of source project numbers.

       --source-projects-file=SOURCE_PROJECT_NUMBERS_IN_FILE
          CSV formatted file containing source project numbers, one per line.

OPTIONAL FLAGS
     --auto-add-new-buckets
        Automatically include any new buckets created if they satisfy criteria
        defined in config settings.

     --description=DESCRIPTION
        Description for dataset config.

     --identity=IDENTITY_TYPE; default="IDENTITY_TYPE_PER_CONFIG"
        The type of service account used in the dataset config. IDENTITY_TYPE
        must be one of: IDENTITY_TYPE_PER_CONFIG, IDENTITY_TYPE_PER_PROJECT.

     Specify the list of buckets to be included or excluded, both a list of
     bucket names and prefix regexes can be specified for either include or
     exclude buckets.

     At most one of these can be specified:

       Specify the list of buckets to be excluded.

         --exclude-bucket-names=[BUCKETS_NAMES,...]
            List of bucket names to be excluded.

         --exclude-bucket-prefix-regexes=[BUCKETS_REGEXES,...]
            List of bucket prefix regexes to be excluded. Allowed regex
            patterns are similar to those for the
            --include-bucket-prefix-regexes flag.

       Specify the list of buckets to be included.

         --include-bucket-names=[BUCKETS_NAMES,...]
            List of bucket names be included.

         --include-bucket-prefix-regexes=[BUCKETS_REGEXES,...]
            List of bucket prefix regexes to be included. The dataset config
            will include all the buckets that match with the prefix regex.
            Examples of allowed prefix regex patterns can be testbucket*,
            testbucket.*foo, testb.+foo* . It should follow syntax specified in
            google/re2 on GitHub.

     Specify the list of locations for source projects to be included or
     excluded.

     At most one of these can be specified:

       --exclude-source-locations=[LIST_OF_SOURCE_LOCATIONS,...]
          List of locations for projects to be excluded.

       --include-source-locations=[LIST_OF_SOURCE_LOCATIONS,...]
          List of locations for projects to be included.

GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
    --help, --impersonate-service-account, --log-http, --project, --quiet,
    --trace-token, --user-output-enabled, --verbosity.

    Run $ gcloud help for details.

NOTES
    This command is currently in alpha and might change without notice. If this
    command fails with API permission errors despite specifying the correct
    project, you might be trying to access an API with an invitation-only early
    access allowlist.

