Skip to content

Commit 1f7bae6

Browse files
aws-sdk-cpp-automationaws-sdk-cpp-automation
committed
Update API model
1 parent ace26dd commit 1f7bae6

49 files changed

Lines changed: 8820 additions & 31 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎tools/code-generation/smithy/api-descriptions/appconfig.json‎

Lines changed: 224 additions & 0 deletions
Large diffs are not rendered by default.

‎tools/code-generation/smithy/api-descriptions/application-signals.json‎

Lines changed: 104 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,110 @@
114114
"aws.protocols#restJson1": {},
115115
"smithy.api#documentation": "<p>Use CloudWatch Application Signals for comprehensive observability of your cloud-based applications. It enables real-time service health dashboards and helps you track long-term performance trends against your business goals. The application-centric view provides you with unified visibility across your applications, services, and dependencies, so you can proactively monitor and efficiently triage any issues that may arise, ensuring optimal customer experience.</p> <p>Application Signals provides the following benefits:</p> <ul> <li> <p>Automatically collect metrics and traces from your applications, and display key metrics such as call volume, availability, latency, faults, and errors. </p> </li> <li> <p>Create and monitor service level objectives (SLOs). </p> </li> <li> <p>See a map of your application topology that Application Signals automatically discovers, that gives you a visual representation of your applications, dependencies, and their connectivity.</p> </li> </ul> <p>Application Signals works with CloudWatch RUM, CloudWatch Synthetics canaries, and Amazon Web Services Service Catalog AppRegistry, to display your client pages, Synthetics canaries, and application names within dashboards and maps.</p>",
116116
"smithy.api#title": "Amazon CloudWatch Application Signals",
117+
"smithy.rules#endpointBdd": {
118+
"version": "1.1",
119+
"parameters": {
120+
"UseFIPS": {
121+
"builtIn": "AWS::UseFIPS",
122+
"required": true,
123+
"default": false,
124+
"documentation": "When true, send this request to the FIPS-compliant regional endpoint. If the configured endpoint does not have a FIPS compliant endpoint, dispatching the request will return an error.",
125+
"type": "boolean"
126+
},
127+
"Endpoint": {
128+
"builtIn": "SDK::Endpoint",
129+
"required": false,
130+
"documentation": "Override the endpoint used to send this request",
131+
"type": "string"
132+
},
133+
"Region": {
134+
"builtIn": "AWS::Region",
135+
"required": false,
136+
"documentation": "The AWS region used to dispatch the request.",
137+
"type": "string"
138+
}
139+
},
140+
"conditions": [
141+
{
142+
"fn": "isSet",
143+
"argv": [
144+
{
145+
"ref": "Endpoint"
146+
}
147+
]
148+
},
149+
{
150+
"fn": "isSet",
151+
"argv": [
152+
{
153+
"ref": "Region"
154+
}
155+
]
156+
},
157+
{
158+
"fn": "aws.partition",
159+
"argv": [
160+
{
161+
"ref": "Region"
162+
}
163+
],
164+
"assign": "PartitionResult"
165+
},
166+
{
167+
"fn": "booleanEquals",
168+
"argv": [
169+
{
170+
"ref": "UseFIPS"
171+
},
172+
true
173+
]
174+
}
175+
],
176+
"results": [
177+
{
178+
"conditions": [],
179+
"error": "Invalid Configuration: FIPS and custom endpoint are not supported",
180+
"type": "error"
181+
},
182+
{
183+
"conditions": [],
184+
"endpoint": {
185+
"url": {
186+
"ref": "Endpoint"
187+
},
188+
"properties": {},
189+
"headers": {}
190+
},
191+
"type": "endpoint"
192+
},
193+
{
194+
"conditions": [],
195+
"endpoint": {
196+
"url": "https://application-signals-fips.{Region}.{PartitionResult#dualStackDnsSuffix}",
197+
"properties": {},
198+
"headers": {}
199+
},
200+
"type": "endpoint"
201+
},
202+
{
203+
"conditions": [],
204+
"endpoint": {
205+
"url": "https://application-signals.{Region}.{PartitionResult#dualStackDnsSuffix}",
206+
"properties": {},
207+
"headers": {}
208+
},
209+
"type": "endpoint"
210+
},
211+
{
212+
"conditions": [],
213+
"error": "Invalid Configuration: Missing Region",
214+
"type": "error"
215+
}
216+
],
217+
"root": 2,
218+
"nodeCount": 6,
219+
"nodes": "/////wAAAAH/////AAAAAAAAAAYAAAADAAAAAQAAAAQF9eEFAAAAAgAAAAUF9eEFAAAAAwX14QMF9eEEAAAAAwX14QEF9eEC"
220+
},
117221
"smithy.rules#endpointRuleSet": {
118222
"version": "1.0",
119223
"parameters": {

‎tools/code-generation/smithy/api-descriptions/b2bi.json‎

Lines changed: 188 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,194 @@
103103
"smithy.api#documentation": "<p>This is the <i>Amazon Web Services B2B Data Interchange API Reference</i>. It provides descriptions, API request parameters, and the XML response for each of the B2BI API actions.</p> <p>B2BI enables automated exchange of EDI (electronic data interchange) based business-critical transactions at cloud scale, with elasticity and pay-as-you-go pricing. Businesses use EDI documents to exchange transactional data with trading partners, such as suppliers and end customers, using standardized formats such as X12.</p> <note> <p>Rather than actually running a command, you can use the <code>--generate-cli-skeleton</code> parameter with any API call to generate and display a parameter template. You can then use the generated template to customize and use as input on a later command. For details, see <a href=\"https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-skeleton.html#cli-usage-skeleton-generate\">Generate and use a parameter skeleton file</a>.</p> </note>",
104104
"smithy.api#title": "AWS B2B Data Interchange",
105105
"smithy.api#unstable": {},
106+
"smithy.rules#endpointBdd": {
107+
"version": "1.1",
108+
"parameters": {
109+
"Region": {
110+
"builtIn": "AWS::Region",
111+
"required": false,
112+
"documentation": "The AWS region used to dispatch the request.",
113+
"type": "string"
114+
},
115+
"UseDualStack": {
116+
"builtIn": "AWS::UseDualStack",
117+
"required": true,
118+
"default": false,
119+
"documentation": "When true, use the dual-stack endpoint. If the configured endpoint does not support dual-stack, dispatching the request MAY return an error.",
120+
"type": "boolean"
121+
},
122+
"UseFIPS": {
123+
"builtIn": "AWS::UseFIPS",
124+
"required": true,
125+
"default": false,
126+
"documentation": "When true, send this request to the FIPS-compliant regional endpoint. If the configured endpoint does not have a FIPS compliant endpoint, dispatching the request will return an error.",
127+
"type": "boolean"
128+
},
129+
"Endpoint": {
130+
"builtIn": "SDK::Endpoint",
131+
"required": false,
132+
"documentation": "Override the endpoint used to send this request",
133+
"type": "string"
134+
}
135+
},
136+
"conditions": [
137+
{
138+
"fn": "isSet",
139+
"argv": [
140+
{
141+
"ref": "Endpoint"
142+
}
143+
]
144+
},
145+
{
146+
"fn": "isSet",
147+
"argv": [
148+
{
149+
"ref": "Region"
150+
}
151+
]
152+
},
153+
{
154+
"fn": "aws.partition",
155+
"argv": [
156+
{
157+
"ref": "Region"
158+
}
159+
],
160+
"assign": "PartitionResult"
161+
},
162+
{
163+
"fn": "booleanEquals",
164+
"argv": [
165+
{
166+
"ref": "UseFIPS"
167+
},
168+
true
169+
]
170+
},
171+
{
172+
"fn": "booleanEquals",
173+
"argv": [
174+
{
175+
"ref": "UseDualStack"
176+
},
177+
true
178+
]
179+
},
180+
{
181+
"fn": "booleanEquals",
182+
"argv": [
183+
{
184+
"fn": "getAttr",
185+
"argv": [
186+
{
187+
"ref": "PartitionResult"
188+
},
189+
"supportsDualStack"
190+
]
191+
},
192+
true
193+
]
194+
},
195+
{
196+
"fn": "booleanEquals",
197+
"argv": [
198+
{
199+
"fn": "getAttr",
200+
"argv": [
201+
{
202+
"ref": "PartitionResult"
203+
},
204+
"supportsFIPS"
205+
]
206+
},
207+
true
208+
]
209+
}
210+
],
211+
"results": [
212+
{
213+
"conditions": [],
214+
"error": "Invalid Configuration: FIPS and custom endpoint are not supported",
215+
"type": "error"
216+
},
217+
{
218+
"conditions": [],
219+
"error": "Invalid Configuration: Dualstack and custom endpoint are not supported",
220+
"type": "error"
221+
},
222+
{
223+
"conditions": [],
224+
"endpoint": {
225+
"url": {
226+
"ref": "Endpoint"
227+
},
228+
"properties": {},
229+
"headers": {}
230+
},
231+
"type": "endpoint"
232+
},
233+
{
234+
"conditions": [],
235+
"endpoint": {
236+
"url": "https://b2bi-fips.{Region}.{PartitionResult#dualStackDnsSuffix}",
237+
"properties": {},
238+
"headers": {}
239+
},
240+
"type": "endpoint"
241+
},
242+
{
243+
"conditions": [],
244+
"error": "FIPS and DualStack are enabled, but this partition does not support one or both",
245+
"type": "error"
246+
},
247+
{
248+
"conditions": [],
249+
"endpoint": {
250+
"url": "https://b2bi-fips.{Region}.{PartitionResult#dnsSuffix}",
251+
"properties": {},
252+
"headers": {}
253+
},
254+
"type": "endpoint"
255+
},
256+
{
257+
"conditions": [],
258+
"error": "FIPS is enabled but this partition does not support FIPS",
259+
"type": "error"
260+
},
261+
{
262+
"conditions": [],
263+
"endpoint": {
264+
"url": "https://b2bi.{Region}.{PartitionResult#dualStackDnsSuffix}",
265+
"properties": {},
266+
"headers": {}
267+
},
268+
"type": "endpoint"
269+
},
270+
{
271+
"conditions": [],
272+
"error": "DualStack is enabled but this partition does not support DualStack",
273+
"type": "error"
274+
},
275+
{
276+
"conditions": [],
277+
"endpoint": {
278+
"url": "https://b2bi.{Region}.{PartitionResult#dnsSuffix}",
279+
"properties": {},
280+
"headers": {}
281+
},
282+
"type": "endpoint"
283+
},
284+
{
285+
"conditions": [],
286+
"error": "Invalid Configuration: Missing Region",
287+
"type": "error"
288+
}
289+
],
290+
"root": 2,
291+
"nodeCount": 13,
292+
"nodes": "/////wAAAAH/////AAAAAAAAAAwAAAADAAAAAQAAAAQF9eELAAAAAgAAAAUF9eELAAAAAwAAAAgAAAAGAAAABAAAAAcF9eEKAAAABQX14QgF9eEJAAAABAAAAAoAAAAJAAAABgX14QYF9eEHAAAABQAAAAsF9eEFAAAABgX14QQF9eEFAAAAAwX14QEAAAANAAAABAX14QIF9eED"
293+
},
106294
"smithy.rules#endpointRuleSet": {
107295
"version": "1.0",
108296
"parameters": {

0 commit comments

Comments
 (0)