Creates and starts a Replay using the given ReplayConfig.

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: policysimulator1 --scope <scope> projects locations-replays-create ...

Required Scalar Argument

• <parent> (string)
  • Required. The parent resource where this Replay will be created. This resource must be a project, folder, or organization with a location. Example: projects/my-example-project/locations/global

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:

GoogleCloudPolicysimulatorV1Replay:
  config:
    log-source: string
  name: string
  results-summary:
    difference-count: integer
    error-count: integer
    log-count: integer
    newest-date:
      day: integer
      month: integer
      year: integer
    oldest-date:
      day: integer
      month: integer
      year: integer
    unchanged-count: integer
  state: 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 .config log-source=eos

  • The logs to use as input for the Replay.

• .. name=labore

  • Output only. The resource name of the Replay, which has the following format: {projects|folders|organizations}/{resource-id}/locations/global/replays/{replay-id}, where {resource-id} is the ID of the project, folder, or organization that owns the Replay. Example: projects/my-example-project/locations/global/replays/506a5f7f-38ce-4d7d-8e03-479ce1833c36
• results-summary difference-count=58
  • The number of replayed log entries with a difference between baseline and simulated policies.
• error-count=31
  • The number of log entries that could not be replayed.
• log-count=21
  • The total number of log entries replayed.
• newest-date day=40
  • Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
• month=86
  • Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

• year=88

  • Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

• ..oldest-date day=77

  • Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant.
• month=58
  • Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day.

• year=77

  • Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year.

• .. unchanged-count=33

  • The number of replayed log entries with no difference between baseline and simulated policies.

• .. state=vero

  • Output only. The current state of the Replay.

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 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").