HumDay

Reschedule maintenance for a given instance in a given project in Google Cloud Memorystore for Redis

A documented Google Cloud Memorystore for Redis operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Reschedule maintenance for a given instance in a given project and location.

  • POSTChanges data · projectsredis.googleapis.com/v1/{name}:rescheduleMaintenance

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Cloud Memorystore for Redis operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Cloud Memorystore for Redis operations

All 14 Google Cloud Memorystore for Redis operations

Questions

Can HumDay reschedule maintenance for a given instance in a given project in Google Cloud Memorystore for Redis?
Yes. This operation is published in Google Cloud Memorystore for Redis's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google Cloud Memorystore for Redis data?
Yes — this is a POST operation, so it changes something in Google Cloud Memorystore for Redis. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Cloud Memorystore for Redis account.

Where this came from

Read from a published API description for Google Cloud Memorystore for Redis at redis.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-03-16.