create_view
async
¶
create_view(
instance_id: ViewsInstanceId,
status: ViewStatus,
content: ViewInputContent,
name: ViewName,
*,
config_overrides: Optional[AsyncConnectClientConfig] = None,
client_token: Optional[ViewsClientToken] = None,
description: Optional[ViewDescription] = None,
tags: Optional[TagMap] = None,
) -> CreateViewResponse
Creates a new view with the possible status of SAVED or PUBLISHED.
The views will have a unique name for each connect instance.
It performs basic content validation if the status is SAVED or full content validation if the status is set to PUBLISHED. An error is returned if validation fails. It associates either the $SAVED qualifier or both of the $SAVED and $LATEST qualifiers with the provided view content based on the status. The view is idempotent if ClientToken is provided.
Parameters:
-
instance_id(ViewsInstanceId) –The identifier of the Connect Customer instance. You can find the instanceId in the ARN of the instance.
-
client_token(Optional[ViewsClientToken], default:None) –A unique Id for each create view request to avoid duplicate view creation. For example, the view is idempotent ClientToken is provided.
-
status(ViewStatus) –Indicates the view status as either
SAVEDorPUBLISHED. ThePUBLISHEDstatus will initiate validation on the content. -
content(ViewInputContent) –View content containing all content necessary to render a view except for runtime input data.
The total uncompressed content has a maximum file size of 400kB.
-
description(Optional[ViewDescription], default:None) –The description of the view.
-
name(ViewName) –The name of the view.
-
tags(Optional[TagMap], default:None) –The tags associated with the view resource (not specific to view version).These tags can be used to organize, track, or control access for this resource. For example, { "tags": {"key1":"value1", "key2":"value2"} }.
Raises:
-
AccessDeniedException–You do not have sufficient permissions to perform this action.
-
DuplicateResourceException–A resource with the specified name already exists.
-
InternalServiceException–Request processing failed because of an error or failure with the service.
-
InvalidParameterException–One or more of the specified parameters are not valid.
-
InvalidRequestException–The request is not valid.
-
ResourceInUseException–That resource is already in use (for example, you're trying to add a record with the same name as an existing record). If you are trying to delete a resource (for example, DeleteHoursOfOperation or DeletePredefinedAttribute), remove its reference from related resources and then try again.
-
ResourceNotFoundException–The specified resource was not found.
-
ServiceQuotaExceededException–The service quota has been exceeded.
-
TooManyRequestsException–Displayed when rate-related API limits are exceeded.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_connect/_services/async_connect.py
6294 6295 6296 6297 6298 6299 6300 6301 6302 6303 6304 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325 6326 6327 6328 6329 6330 6331 6332 6333 6334 6335 6336 6337 6338 6339 6340 6341 6342 6343 6344 6345 6346 6347 6348 6349 6350 6351 6352 6353 6354 6355 6356 6357 6358 6359 6360 6361 6362 6363 6364 6365 6366 6367 6368 6369 6370 6371 6372 6373 6374 6375 6376 6377 6378 6379 6380 6381 6382 6383 6384 6385 6386 6387 6388 | |