Modify the specified resource policy.


You will need authorization for at least one of the following scopes to make a valid call:


If unset, the scope for this method defaults to You can set the scope for this method like this: compute1 --scope <scope> resource-policies patch ...

Required Scalar Arguments

  • <project> (string)
    • Project ID for this request.
  • <region> (string)
    • Name of the region for this request.
  • <resource-policy> (string)
    • Id of the resource policy to patch.

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:

  creation-timestamp: string
  description: string
    availability-domain-count: integer
    collocation: string
    vm-count: integer
  id: string
    expiration-time: string
    start-time: string
    time-zone: string
      schedule: string
      schedule: string
  kind: string
  name: string
  region: string
      last-run-start-time: string
      next-run-start-time: string
  self-link: string
      max-retention-days: integer
      on-source-disk-delete: string
        days-in-cycle: integer
        duration: string
        start-time: string
        duration: string
        hours-in-cycle: integer
        start-time: string
      chain-name: string
      guest-flush: boolean
      labels: { string: string }
      storage-locations: [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 . creation-timestamp=sadipscing
    • [Output Only] Creation timestamp in RFC3339 text format.
  • description=sit
    • No description provided.
  • group-placement-policy availability-domain-count=42
    • The number of availability domains to spread instances across. If two instances are in different availability domain, they are not in the same low latency network.
  • collocation=et
    • Specifies network collocation
  • vm-count=79

    • Number of VMs in this placement group. Google does not recommend that you use this field unless you use a compact policy and you want your policy to work only if it contains this exact number of VMs.
  • .. id=et

    • [Output Only] The unique identifier for the resource. This identifier is defined by the server.
  • instance-schedule-policy expiration-time=vero
    • The expiration time of the schedule. The timestamp is an RFC3339 string.
  • start-time=diam
    • The start time of the schedule. The timestamp is an RFC3339 string.
  • time-zone=takimata
    • Specifies the time zone to be used in interpreting Schedule.schedule. The value of this field must be a time zone name from the tz database:
  • vm-start-schedule schedule=est

    • Specifies the frequency for the operation, using the unix-cron format.
  • ..vm-stop-schedule schedule=invidunt

    • Specifies the frequency for the operation, using the unix-cron format.
  • ... kind=ut

    • [Output Only] Type of the resource. Always compute#resource_policies for resource policies.
  • name=nonumy
    • The name of the resource, provided by the client when initially creating the resource. The resource name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression [a-z]([-a-z0-9]*[a-z0-9])? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
  • region=diam
    • No description provided.
  • resource-status.instance-schedule-policy last-run-start-time=accusam
    • [Output Only] The last time the schedule successfully ran. The timestamp is an RFC3339 string.
  • next-run-start-time=nonumy

    • [Output Only] The next time the schedule is planned to run. The actual time might be slightly different. The timestamp is an RFC3339 string.
  • ... self-link=voluptua.

    • [Output Only] Server-defined fully-qualified URL for this resource.
  • snapshot-schedule-policy.retention-policy max-retention-days=92
    • Maximum age of the snapshot that is allowed to be kept.
  • on-source-disk-delete=justo

    • Specifies the behavior to apply to scheduled snapshots when the source disk is deleted.
  • ..schedule.daily-schedule days-in-cycle=27

    • Defines a schedule with units measured in days. The value determines how many days pass between the start of each cycle.
  • duration=sea
    • [Output only] A predetermined duration for the window, automatically chosen to be the smallest possible in the given scenario.
  • start-time=nonumy

    • Start time of the window. This must be in UTC format that resolves to one of 00:00, 04:00, 08:00, 12:00, 16:00, or 20:00. For example, both 13:00-5 and 08:00 are valid.
  • ..hourly-schedule duration=elitr

    • [Output only] Duration of the time window, automatically chosen to be smallest possible in the given scenario.
  • hours-in-cycle=53
    • Defines a schedule with units measured in hours. The value determines how many hours pass between the start of each cycle.
  • start-time=labore

    • Time within the window to start the operations. It must be in format "HH:MM", where HH : [00-23] and MM : [00-00] GMT.
  • ...snapshot-properties chain-name=ut

    • Chain name that the snapshot is created in.
  • guest-flush=false
    • Indication to perform a 'guest aware' snapshot.
  • labels=key=diam
    • Labels to apply to scheduled snapshots. These can be later modified by the setLabels method. Label values may be empty.
    • the value will be associated with the given key
  • storage-locations=nonumy

    • Cloud Storage bucket storage location of the auto snapshot (regional or multi-regional).
    • Each invocation of this argument appends the given value to the array.
  • ... status=lorem

    • [Output Only] The status of resource policy creation.

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 request-id=string

    • An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).
  • -p update-mask=string

    • update_mask indicates fields to be updated as part of this request.

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").
  • -p user-ip=string

    • Legacy name for parameter that has been superseded by quotaUser.