gcloud alpha developer-connect account-connectors create - create accountConnectors

gcloud alpha developer-connect account-connectors create(ACCOUNT_CONNECTOR :--location=LOCATION)[--annotations=[ANNOTATIONS,…]][--async][--etag=ETAG][--labels=[LABELS,…]][--request-id=REQUEST_ID][--validate-only][--provider-oauth-config-scopes=[PROVIDER_OAUTH_CONFIG_SCOPES,…] :--provider-oauth-config-system-id=PROVIDER_OAUTH_CONFIG_SYSTEM_ID][GCLOUD_WIDE_FLAG …]

AccountConnector resource - Identifier. The resource name of theaccountConnector, in the formatprojects/{project}/locations/{location}/accountConnectors/{account_connector_id}.The arguments in this group can be used to specify the attributes of thisresource. (NOTE) Some attributes are not given arguments in this group but canbe set in other ways.

To set theproject attribute:

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

This must be specified.

ACCOUNT_CONNECTOR

ID of the accountConnector or fully qualified identifier for theaccountConnector.

To set theaccount_connector attribute:

• provide the argumentaccount_connector on the command line.

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

--location=LOCATION

The location id of the accountConnector resource.

To set thelocation attribute:

• provide the argumentaccount_connector on the command line with afully specified name;
• provide the argument--location on the command line.

--annotations=[ANNOTATIONS,…]

Allows users to store small amounts of arbitrary data.

KEY

SetsKEY value.

VALUE

SetsVALUE value.

Shorthand Example:

--annotations=string=string

JSON Example:

--annotations='{"string": "string"}'

File Example:

--annotations=path_to_file.(yaml|json)

--async

Return immediately, without waiting for the operation in progress to complete.

--etag=ETAG

This checksum is computed by the server based on the value of other fields, andmay be sent on update and delete requests to ensure the client has an up-to-datevalue before proceeding.

--labels=[LABELS,…]

Labels as key value pairs.

KEY

Keys must start with a lowercase character and contain only hyphens(-), underscores (_), lowercase characters, andnumbers.

VALUE

Values must contain only hyphens (-), underscores (_),lowercase characters, and numbers.

Shorthand Example:

--labels=string=string

JSON Example:

--labels='{"string": "string"}'

File Example:

--labels=path_to_file.(yaml|json)

--request-id=REQUEST_ID

An optional request ID to identify requests. Specify a unique request ID so thatif you must retry your request, the server will know to ignore the request if ithas already been completed. The server will guarantee that for at least 60minutes since the first request.

For example, consider a situation where you make an initial request and therequest times out. If you make the request again with the same request ID, theserver can check if original operation with the same request ID was received,and if so, will ignore the second request. This prevents clients fromaccidentally creating duplicate commitments.

The request ID must be a valid UUID with the exception that zero UUID is notsupported (00000000-0000-0000-0000-000000000000).

--validate-only

If set, validate the request, but do not actually post it.

Arguments for the account connector config.

At most one of these can be specified:

ProviderOAuthConfig is the OAuth config for a provider.

--provider-oauth-config-scopes=[PROVIDER_OAUTH_CONFIG_SCOPES,…]

User selected scopes to apply to the Oauth config In the event of changingscopes, user records under AccountConnector will be deleted and users willre-auth again.

This flag argument must be specified if any of the other arguments in this groupare specified.

Arguments for the oauth provider id.

--provider-oauth-config-system-id=PROVIDER_OAUTH_CONFIG_SYSTEM_ID

Developer Connect provided OAuth.PROVIDER_OAUTH_CONFIG_SYSTEM_ID must be one of:

datastax

Datastax provider. No scopes are allowed.

dynatrace

Dynatrace provider.

github

GitHub provider. Scopes can be found athttps://docs.github.com/en/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes

gitlab

GitLab provider. Scopes can be found athttps://docs.gitlab.com/user/profile/personal_access_tokens/#personal-access-token-scopes

google

Google provider. Recommended scopes:"https://www.googleapis.com/auth/drive.readonly","https://www.googleapis.com/auth/documents.readonly"

new-relic

New Relic provider. No scopes are allowed.

rovo

Rovo provider. Must select the "rovo" scope.

sentry

Sentry provider. Scopes can be found athttps://docs.sentry.io/api/permissions/

Run$gcloud help for details.