Updates the details for an AppGroup app. In addition, you can add an API product to an AppGroup app and automatically generate an API key for the app to use when calling APIs in the API product. If you want to use an existing API key for the API product, add the API product to the API key using the UpdateAppGroupAppKey API. Using this API, you cannot update the app name, as it is the primary key used to identify the app and cannot be changed. This API replaces the existing attributes with those specified in the request. Include or exclude any existing attributes that you want to retain or delete, respectively.

Scopes

You will need authorization for the https://www.googleapis.com/auth/cloud-platform scope to make a valid call.

If unset, the scope for this method defaults to https://www.googleapis.com/auth/cloud-platform. You can set the scope for this method like this: apigee1 --scope <scope> organizations appgroups-apps-update ...

Required Scalar Argument

• <name> (string)
  • Required. Name of the AppGroup app. Use the following structure in your request: organizations/{org}/appgroups/{app_group_name}/apps/{app}

Required Request Value

The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.

For example, a structure like this:

GoogleCloudApigeeV1AppGroupApp:
  api-products: [string]
  app-group: string
  app-id: string
  callback-url: string
  created-at: string
  key-expires-in: string
  last-modified-at: string
  name: string
  scopes: [string]
  status: string

can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.

• -r . api-products=lorem
  • List of API products associated with the AppGroup app.
  • Each invocation of this argument appends the given value to the array.
• app-group=accusam
  • Immutable. Name of the parent AppGroup whose resource name format is of syntax (organizations//appgroups/).
• app-id=amet
  • Immutable. ID of the AppGroup app.
• callback-url=erat
  • Callback URL used by OAuth 2.0 authorization servers to communicate authorization codes back to AppGroup apps.
• created-at=dolores
  • Output only. Time the AppGroup app was created in milliseconds since epoch.
• key-expires-in=erat
  • Immutable. Expiration time, in seconds, for the consumer key that is generated for the AppGroup app. If not set or left to the default value of -1, the API key never expires. The expiration time can't be updated after it is set.
• last-modified-at=accusam
  • Output only. Time the AppGroup app was modified in milliseconds since epoch.
• name=sea
  • Immutable. Name of the AppGroup app whose resource name format is of syntax (organizations//appgroups//apps/*).
• scopes=takimata
  • Scopes to apply to the AppGroup app. The specified scopes must already exist for the API product that you associate with the AppGroup app.
  • Each invocation of this argument appends the given value to the array.
• status=lorem
  • Status of the App. Valid values include approved or revoked.

About Cursors

The cursor position is key to comfortably set complex nested structures. The following rules apply:

• The cursor position is always set relative to the current one, unless the field name starts with the . character. Fields can be nested such as in -r f.s.o .
• The cursor position is set relative to the top-level structure if it starts with ., e.g. -r .s.s
• You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify -r struct.sub_struct=bar.
• You can move the cursor one level up by using ... Each additional . moves it up one additional level. E.g. ... would go three levels up.

Optional Output Flags

The method's return value a JSON encoded structure, which will be written to standard output by default.

• -o out
  • out specifies the destination to which to write the server's result to. It will be a JSON-encoded structure. The destination may be - to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.

Optional Method Properties

You may set the following properties to further configure the call. Please note that -p is followed by one or more key-value-pairs, and is called like this -p k1=v1 k2=v2 even though the listing below repeats the -p for completeness.

• -p action=string
  • Approve or revoke the consumer key by setting this value to approve or revoke. The Content-Type header must be set to application/octet-stream, with empty body.

Optional General Properties

The following properties can configure any call, and are not specific to this method.

• -p $-xgafv=string

  • V1 error format.

• -p access-token=string

  • OAuth access token.

• -p alt=string

  • Data format for response.

• -p callback=string

  • JSONP

• -p fields=string

  • Selector specifying which fields to include in a partial response.

• -p key=string

  • API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.

• -p oauth-token=string

  • OAuth 2.0 token for the current user.

• -p pretty-print=boolean

  • Returns response with indentations and line breaks.

• -p quota-user=string

  • Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.

• -p upload-type=string

  • Legacy upload protocol for media (e.g. "media", "multipart").

• -p upload-protocol=string

  • Upload protocol for media (e.g. "raw", "multipart").