NAME
    gcloud beta developer-connect insights-configs create - create an insight
        config

SYNOPSIS
    gcloud beta developer-connect insights-configs create
        (INSIGHTS_CONFIG : --location=LOCATION)
        (--app-hub-application=APP_HUB_APPLICATION
          | --target-projects=[TARGET_PROJECTS,...])
        [--artifact-config=ARTIFACT_CONFIG_ITEM]
        [--source-config=[SOURCE_CONFIG,...]] [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (BETA) Create an insights config.

EXAMPLES
    To create an insights config with an apphub application, run:

        $ gcloud beta developer-connect insights-configs create \
            insights-config-name \
            --app-hub-application=projects/my-project/locations/\
        us-central1/applications/my-app-hub-application

    To create an insights config with projects, run:

        $ gcloud beta developer-connect insights-configs create \
            insights-config-name --target-projects=project1,project2

POSITIONAL ARGUMENTS
     Insights config resource - The insights config to create. The arguments in
     this group can be used to specify the attributes of this resource. (NOTE)
     Some attributes are not given arguments in this group but can be set in
     other ways.

     To set the project attribute:
      ◆ provide the argument insights_config on the command line with a fully
        specified name;
      ◆ provide the argument --project on the command line;
      ◆ set the property core/project.

     This must be specified.

       INSIGHTS_CONFIG
          ID of the insights_config or fully qualified identifier for the
          insights_config.

          To set the insightsConfigs attribute:
          ▸ provide the argument insights_config on the command line.

          This positional argument must be specified if any of the other
          arguments in this group are specified.

       --location=LOCATION
          The region of the insight config.

          To set the location attribute:
          ▸ provide the argument insights_config on the command line with a
            fully specified name;
          ▸ provide the argument --location on the command line.

REQUIRED FLAGS
     Exactly one of these must be specified:

       --app-hub-application=APP_HUB_APPLICATION
          The App Hub application to which the insight config is associated.

       --target-projects=[TARGET_PROJECTS,...]
          A comma-separated list of target project IDs/numbers to which the
          insight config is associated.

          Format examples: --target-projects=123567890,my-project
          --target-projects=projects/1234567890,projects/my-project

OPTIONAL FLAGS
     --artifact-config=ARTIFACT_CONFIG_ITEM
        Specifies a single artifact configuration. This flag can be repeated
        for multiple configurations.

        Each configuration can be provided in a key-value format.

        Format examples:
        --artifact-config=uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project
        --artifact-config=[uri={REGION}-docker.pkg.dev/my-project/my-repo/my-image,buildProject=my-project]

        Supported keys within a configuration:
        ◆ buildProject: String, e.g., my-project
        ◆ uri: String, e.g.,
          {REGION}-docker.pkg.dev/my-project/my-repo/my-image

     --source-config=[SOURCE_CONFIG,...]
        The source config of the git repository link.

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 beta and might change without notice. These
    variants are also available:

        $ gcloud developer-connect insights-configs create

        $ gcloud alpha developer-connect insights-configs create

