gcloud beta developer-connect insights-configs create

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][GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) Create an insights config.
EXAMPLES
To create an insights config with an apphub application, run:
gcloudbetadeveloper-connectinsights-configscreateinsights-config-name--app-hub-application=projects/my-project/locations/us-central1/applications/my-app-hub-application

To create an insights config with projects, run:

gcloudbetadeveloper-connectinsights-configscreateinsights-config-name--target-projects=project1,project2
POSITIONAL ARGUMENTS
Insights config resource - The insights config to create. The arguments in thisgroup can be used to specify the attributes of this resource. (NOTE) Someattributes are not given arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumentinsights_config on the command line with afully specified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

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

To set theinsightsConfigs attribute:

  • provide the argumentinsights_config on the command line.

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

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

To set thelocation attribute:

  • provide the argumentinsights_config on the command line with afully 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 configis 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 formultiple 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
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. Thesevariants are also available:
gclouddeveloper-connectinsights-configscreate
gcloudalphadeveloper-connectinsights-configscreate

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-16 UTC.