You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(gamelift): add MatchmakingConfiguration L2 Construct for GameLift (#23326)
Following aws/aws-cdk-rfcs#436 I have written the Gamelift QueuedMatchmakingConfiguration and StandaloneMatchmakingConfiguration L2 constructs which create all related resources.
----
### All Submissions:
* [x] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md)
### Adding new Construct Runtime Dependencies:
* [ ] This PR adds new construct runtime dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-construct-runtime-dependencies)
### New Features
* [x] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)?
* [x] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)?
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
* @default no notification target binded to imported ressource
124
+
*/
125
+
readonlynotificationTarget?: sns.ITopic;
126
+
}
127
+
128
+
/**
129
+
* Properties for a new Gamelift matchmaking configuration
130
+
*/
131
+
exportinterfaceMatchmakingConfigurationProps{
132
+
133
+
/**
134
+
* A unique identifier for the matchmaking configuration.
135
+
* This name is used to identify the configuration associated with a matchmaking request or ticket.
136
+
*/
137
+
readonlymatchmakingConfigurationName: string;
138
+
139
+
/**
140
+
* A human-readable description of the matchmaking configuration.
141
+
*
142
+
* @default no description is provided
143
+
*/
144
+
readonlydescription?: string;
145
+
146
+
/**
147
+
* A flag that determines whether a match that was created with this configuration must be accepted by the matched players.
148
+
* With this option enabled, matchmaking tickets use the status `REQUIRES_ACCEPTANCE` to indicate when a completed potential match is waiting for player acceptance.
149
+
*
150
+
* @default Acceptance is not required
151
+
*/
152
+
readonlyrequireAcceptance?: boolean;
153
+
154
+
/**
155
+
* The length of time (in seconds) to wait for players to accept a proposed match, if acceptance is required.
156
+
*
157
+
* @default 300 seconds
158
+
*/
159
+
readonlyacceptanceTimeout?: cdk.Duration;
160
+
161
+
/**
162
+
* Information to add to all events related to the matchmaking configuration.
163
+
*
164
+
* @default no custom data added to events
165
+
*/
166
+
readonlycustomEventData?: string;
167
+
168
+
/**
169
+
* An SNS topic ARN that is set up to receive matchmaking notifications.
0 commit comments