add_group_member
async
¶
add_group_member(
directory_id: DirectoryId,
group_name: GroupName,
member_name: MemberName,
*,
config_overrides: Optional[AsyncDirectoryServiceDataClientConfig] = None,
member_realm: Optional[Realm] = None,
client_token: Optional[ClientToken] = None,
) -> AddGroupMemberResult
Adds an existing user, group, or computer as a group member.
Parameters:
-
directory_id(DirectoryId) –The identifier (ID) of the directory that's associated with the group.
-
group_name(GroupName) –The name of the group.
-
member_name(MemberName) –The
SAMAccountNameof the user, group, or computer to add as a group member. -
member_realm(Optional[Realm], default:None) –The domain name that's associated with the group member. This parameter is required only when adding a member outside of your Managed Microsoft AD domain to a group inside of your Managed Microsoft AD domain. This parameter defaults to the Managed Microsoft AD domain.
This parameter is case insensitive.
-
client_token(Optional[ClientToken], default:None) –A unique and case-sensitive identifier that you provide to make sure the idempotency of the request, so multiple identical calls have the same effect as one single call.
A client token is valid for 8 hours after the first request that uses it completes. After 8 hours, any request with the same client token is treated as a new request. If the request succeeds, any future uses of that token will be idempotent for another 8 hours.
If you submit a request with the same client token but change one of the other parameters within the 8-hour idempotency window, Directory Service Data returns an
ConflictException.This parameter is optional when using the CLI or SDK.
Raises:
-
AccessDeniedException–You don't have permission to perform the request or access the directory. It can also occur when the
DirectoryIddoesn't exist or the user, member, or group might be outside of your organizational unit (OU).Make sure that you have the authentication and authorization to perform the action. Review the directory information in the request, and make sure that the object isn't outside of your OU.
-
ConflictException–This error will occur when you try to create a resource that conflicts with an existing object. It can also occur when adding a member to a group that the member is already in.
This error can be caused by a request sent within the 8-hour idempotency window with the same client token but different input parameters. Client tokens should not be re-used across different requests. After 8 hours, any request with the same client token is treated as a new request.
-
DirectoryUnavailableException–The request could not be completed due to a problem in the configuration or current state of the specified directory.
-
InternalServerException–The operation didn't succeed because an internal error occurred. Try again later.
-
ResourceNotFoundException–The resource couldn't be found.
-
ThrottlingException–The limit on the number of requests per second has been exceeded.
-
ValidationException–The request isn't valid. Review the details in the error message to update the invalid parameters or values in your request.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To add a member to the Marketing group The following command adds an existing user to the Marketing group in the europe.example.com domain.
>>> await client.add_group_member(client_token='550e8400-e29b-41d4-a716-446655440000', directory_id='d-12233abcde', group_name='Marketing', member_name='Pat Candella', member_realm='europe.example.com')
Source code in docs_src/capo_directory_service_data/_services/async_directory_service_data.py
202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 | |