Update the ContainerThreatDetectionSettings resource in Google Security Command Center
A documented Google Security Command Center operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Update the ContainerThreatDetectionSettings resource.
- PATCHChanges data · projects
securitycenter.googleapis.com/v1beta2/{name}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Google Security Command Center operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Google Security Command Center operations
Questions
- Can HumDay update the containerthreatdetectionsettings resource in Google Security Command Center?
- Yes. This operation is published in Google Security Command Center'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 Security Command Center data?
- Yes — this is a PATCH operation, so it changes something in Google Security Command Center. 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 Security Command Center account.
Where this came from
Read from a published API description for Google Security Command Center at securitycenter.googleapis.com/$discovery/rest?version=v1beta2. The description above is the provider’s own wording, not ours. Last published 2023-04-21.