start_engagement_by_accepting_invitation_task
async
¶
start_engagement_by_accepting_invitation_task(
catalog: CatalogIdentifier,
client_token: ClientToken,
identifier: EngagementInvitationArnOrIdentifier,
*,
config_overrides: Optional[AsyncPartnerCentralSellingClientConfig] = None,
tags: Optional[TagList] = None,
) -> StartEngagementByAcceptingInvitationTaskResponse
This action starts the engagement by accepting an EngagementInvitation. The task is asynchronous and involves the following steps: accepting the invitation, creating an opportunity in the partner’s account from the AWS opportunity, and copying details for tracking. When completed, an Opportunity Created event is generated, indicating that the opportunity has been successfully created in the partner's account.
Parameters:
-
catalog(CatalogIdentifier) –Specifies the catalog related to the task. Use
AWSfor production engagements andSandboxfor testing scenarios. -
client_token(ClientToken) –A unique, case-sensitive identifier provided by the client that helps to ensure the idempotency of the request. This can be a random or meaningful string but must be unique for each request.
-
identifier(EngagementInvitationArnOrIdentifier) –Specifies the unique identifier of the
EngagementInvitationto be accepted. Providing the correct identifier helps ensure that the correct engagement is processed. -
tags(Optional[TagList], default:None) –A map of the key-value pairs of the tag or tags to assign.
Raises:
-
AccessDeniedException–This error occurs when you don't have permission to perform the requested action.
You don’t have access to this action or resource. Review IAM policies or contact your AWS administrator for assistance.
-
ConflictException–This error occurs when the request can’t be processed due to a conflict with the target resource's current state, which could result from updating or deleting the resource.
Suggested action: Fetch the latest state of the resource, verify the state, and retry the request.
-
InternalServerException–This error occurs when the specified resource can’t be found or doesn't exist. Resource ID and type might be incorrect.
Suggested action: This is usually a transient error. Retry after the provided retry delay or a short interval. If the problem persists, contact AWS support.
-
ResourceNotFoundException–This error occurs when the specified resource can't be found. The resource might not exist, or isn't visible with the current credentials.
Suggested action: Verify that the resource ID is correct and the resource is in the expected AWS region. Check IAM permissions for accessing the resource.
-
ServiceQuotaExceededException–This error occurs when the request would cause a service quota to be exceeded. Service quotas represent the maximum allowed use of a specific resource, and this error indicates that the request would surpass that limit.
Suggested action: Review the Quotas for the resource, and either reduce usage or request a quota increase.
-
ThrottlingException–This error occurs when there are too many requests sent. Review the provided quotas and adapt your usage to avoid throttling.
This error occurs when there are too many requests sent. Review the provided Quotas and retry after the provided delay.
-
ValidationException–The input fails to satisfy the constraints specified by the service or business validation rules.
Suggested action: Review the error message, including the failed fields and reasons, to correct the request payload.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_partnercentral_selling/_services/async_partner_central_selling.py
1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 | |