public sealed class DeleteUserRequest : IMessage<DeleteUserRequest>, IEquatable<DeleteUserRequest>, IDeepCloneable<DeleteUserRequest>, IBufferMessage, IMessage
Reference documentation and code samples for the AlloyDB v1 API class DeleteUserRequest.
Optional. 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. The server will
guarantee that for at least 60 minutes after the first request.
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).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis document provides reference information for the \u003ccode\u003eDeleteUserRequest\u003c/code\u003e class within the Google.Cloud.AlloyDb.V1 API, detailing its purpose, which is to serve as a message for deleting a user.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eDeleteUserRequest\u003c/code\u003e class implements several interfaces, including \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, indicating its role in message handling and object management.\u003c/p\u003e\n"],["\u003cp\u003eThe class has multiple properties such as \u003ccode\u003eName\u003c/code\u003e, \u003ccode\u003eRequestId\u003c/code\u003e, \u003ccode\u003eUserName\u003c/code\u003e, and \u003ccode\u003eValidateOnly\u003c/code\u003e, allowing for specification of the user to be deleted, request identification, and validation options, respectively.\u003c/p\u003e\n"],["\u003cp\u003eThe document outlines the available constructors for \u003ccode\u003eDeleteUserRequest\u003c/code\u003e, one default and one that copies the properties of an existing \u003ccode\u003eDeleteUserRequest\u003c/code\u003e object, providing flexibility for object creation.\u003c/p\u003e\n"],["\u003cp\u003eThe document lists all previous versions of the API from 1.0.0 to 1.9.0, with 1.9.0 being the latest, and 1.8.0 which is the current version of the \u003ccode\u003eDeleteUserRequest\u003c/code\u003e being documented.\u003c/p\u003e\n"]]],[],null,[]]
