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
Update to ACK runtime v0.39.0, code-generator v0.39.1 (#110)
### Update to ACK runtime `v0.39.0`, code-generator `v0.39.1`
----------
* ACK code-generator `v0.39.1` [release notes](https://github.com/aws-controllers-k8s/code-generator/releases/tag/v0.39.1)
* ACK runtime `v0.39.0` [release notes](https://github.com/aws-controllers-k8s/runtime/releases/tag/v0.39.0)
----------
NOTE:
This PR increments the release version of service controller from `v1.2.14` to `v1.2.15`
Once this PR is merged, release `v1.2.15` will be automatically created for `dynamodb-controller`
**Please close this PR, if you do not want the new patch release for `dynamodb-controller`**
----------
#### stdout for `make build-controller`:
```
building ack-generate ... ok.
==== building dynamodb-controller ====
Copying common custom resource definitions into dynamodb
Building Kubernetes API objects for dynamodb
Generating deepcopy code for dynamodb
Generating custom resource definitions for dynamodb
Building service controller for dynamodb
Generating RBAC manifests for dynamodb
Running gofmt against generated code for dynamodb
Updating additional GitHub repository maintenance files
==== building dynamodb-controller release artifacts ====
Building release artifacts for dynamodb-v1.2.15
Generating common custom resource definitions
Generating custom resource definitions for dynamodb
Generating RBAC manifests for dynamodb
```
----------
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Controls how you are charged for read and write throughput and how you manage
75
75
capacity. This setting can be changed later.
76
76
77
-
78
77
* PROVISIONED - We recommend using PROVISIONED for predictable workloads.
79
78
PROVISIONED sets the billing mode to Provisioned Mode (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html#HowItWorks.ProvisionedThroughput.Manual).
80
79
81
-
82
80
* PAY_PER_REQUEST - We recommend using PAY_PER_REQUEST for unpredictable
83
81
workloads. PAY_PER_REQUEST sets the billing mode to On-Demand Mode (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html#HowItWorks.OnDemand).
84
82
type: string
@@ -99,14 +97,11 @@ spec:
99
97
One or more global secondary indexes (the maximum is 20) to be created on
100
98
the table. Each global secondary index in the array includes the following:
101
99
102
-
103
100
* IndexName - The name of the global secondary index. Must be unique only
104
101
for this table.
105
102
106
-
107
103
* KeySchema - Specifies the key schema for the global secondary index.
108
104
109
-
110
105
* Projection - Specifies attributes that are copied (projected) from the
111
106
table into the index. These are in addition to the primary key attributes
112
107
and index key attributes, which are automatically projected. Each attribute
@@ -121,7 +116,6 @@ spec:
121
116
the same attribute into two different indexes, this counts as two distinct
122
117
attributes when determining the total.
123
118
124
-
125
119
* ProvisionedThroughput - The provisioned throughput settings for the
126
120
global secondary index, consisting of read and write capacity units.
127
121
items:
@@ -135,13 +129,11 @@ spec:
135
129
Represents a single element of a key schema. A key schema specifies the attributes
136
130
that make up the primary key of a table, or the key attributes of an index.
137
131
138
-
139
132
A KeySchemaElement represents exactly one attribute of the primary key. For
140
133
example, a simple primary key would be represented by one KeySchemaElement
141
134
(for the partition key). A composite primary key would require one KeySchemaElement
142
135
for the partition key, and another KeySchemaElement for the sort key.
143
136
144
-
145
137
A KeySchemaElement must be a scalar, top-level attribute (not a nested attribute).
146
138
The data type must be one of String, Number, or Binary. The attribute cannot
147
139
be nested within a List or a Map.
@@ -170,7 +162,6 @@ spec:
170
162
Represents the provisioned throughput settings for a specified table or index.
171
163
The settings can be modified using the UpdateTable operation.
172
164
173
-
174
165
For current minimum and maximum provisioned throughput values, see Service,
175
166
Account, and Table Quotas (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html)
176
167
in the Amazon DynamoDB Developer Guide.
@@ -191,51 +182,41 @@ spec:
191
182
array. For more information, see Data Model (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DataModel.html)
192
183
in the Amazon DynamoDB Developer Guide.
193
184
194
-
195
185
Each KeySchemaElement in the array is composed of:
196
186
197
-
198
187
* AttributeName - The name of this key attribute.
199
188
200
-
201
189
* KeyType - The role that the key attribute will assume: HASH - partition
202
190
key RANGE - sort key
203
191
204
-
205
192
The partition key of an item is also known as its hash attribute. The term
206
193
"hash attribute" derives from the DynamoDB usage of an internal hash function
207
194
to evenly distribute data items across partitions, based on their partition
208
195
key values.
209
196
210
-
211
197
The sort key of an item is also known as its range attribute. The term "range
212
198
attribute" derives from the way DynamoDB stores items with the same partition
213
199
key physically close together, in sorted order by the sort key value.
214
200
215
-
216
201
For a simple primary key (partition key), you must provide exactly one element
217
202
with a KeyType of HASH.
218
203
219
-
220
204
For a composite primary key (partition key and sort key), you must provide
221
205
exactly two elements, in this order: The first element must have a KeyType
222
206
of HASH, and the second element must have a KeyType of RANGE.
223
207
224
-
225
208
For more information, see Working with Tables (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#WorkingWithTables.primary.key)
226
209
in the Amazon DynamoDB Developer Guide.
227
210
items:
228
211
description: |-
229
212
Represents a single element of a key schema. A key schema specifies the attributes
230
213
that make up the primary key of a table, or the key attributes of an index.
231
214
232
-
233
215
A KeySchemaElement represents exactly one attribute of the primary key. For
234
216
example, a simple primary key would be represented by one KeySchemaElement
235
217
(for the partition key). A composite primary key would require one KeySchemaElement
236
218
for the partition key, and another KeySchemaElement for the sort key.
237
219
238
-
239
220
A KeySchemaElement must be a scalar, top-level attribute (not a nested attribute).
240
221
The data type must be one of String, Number, or Binary. The attribute cannot
241
222
be nested within a List or a Map.
@@ -253,18 +234,14 @@ spec:
253
234
GB size limit per partition key value; otherwise, the size of a local secondary
254
235
index is unconstrained.
255
236
256
-
257
237
Each local secondary index in the array includes the following:
258
238
259
-
260
239
* IndexName - The name of the local secondary index. Must be unique only
261
240
for this table.
262
241
263
-
264
242
* KeySchema - Specifies the key schema for the local secondary index.
265
243
The key schema must begin with the same partition key as the table.
266
244
267
-
268
245
* Projection - Specifies attributes that are copied (projected) from the
269
246
table into the index. These are in addition to the primary key attributes
270
247
and index key attributes, which are automatically projected. Each attribute
@@ -289,13 +266,11 @@ spec:
289
266
Represents a single element of a key schema. A key schema specifies the attributes
290
267
that make up the primary key of a table, or the key attributes of an index.
291
268
292
-
293
269
A KeySchemaElement represents exactly one attribute of the primary key. For
294
270
example, a simple primary key would be represented by one KeySchemaElement
295
271
(for the partition key). A composite primary key would require one KeySchemaElement
296
272
for the partition key, and another KeySchemaElement for the sort key.
297
273
298
-
299
274
A KeySchemaElement must be a scalar, top-level attribute (not a nested attribute).
300
275
The data type must be one of String, Number, or Binary. The attribute cannot
301
276
be nested within a List or a Map.
@@ -326,11 +301,9 @@ spec:
326
301
Represents the provisioned throughput settings for a specified table or index.
327
302
The settings can be modified using the UpdateTable operation.
328
303
329
-
330
304
If you set BillingMode as PROVISIONED, you must specify this property. If
331
305
you set BillingMode as PAY_PER_REQUEST, you cannot specify this property.
332
306
333
-
334
307
For current minimum and maximum provisioned throughput values, see Service,
335
308
Account, and Table Quotas (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html)
336
309
in the Amazon DynamoDB Developer Guide.
@@ -356,11 +329,9 @@ spec:
356
329
description: |-
357
330
The settings for DynamoDB Streams on the table. These settings consist of:
358
331
359
-
360
332
* StreamEnabled - Indicates whether DynamoDB Streams is to be enabled
361
333
(true) or disabled (false).
362
334
363
-
364
335
* StreamViewType - When an item in the table is modified, StreamViewType
365
336
determines what information is written to the table's stream. Valid values
366
337
for StreamViewType are: KEYS_ONLY - Only the key attributes of the modified
@@ -391,14 +362,12 @@ spec:
391
362
Describes a tag. A tag is a key-value pair. You can add up to 50 tags to
392
363
a single DynamoDB table.
393
364
394
-
395
365
Amazon Web Services-assigned tag names and values are automatically assigned
396
366
the aws: prefix, which the user cannot assign. Amazon Web Services-assigned
397
367
tag names do not count towards the tag limit of 50. User-assigned tag names
398
368
have the prefix user: in the Cost Allocation Report. You cannot backdate
399
369
the application of a tag.
400
370
401
-
402
371
For an overview on tagging DynamoDB resources, see Tagging for DynamoDB (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html)
403
372
in the Amazon DynamoDB Developer Guide.
404
373
properties:
@@ -440,7 +409,6 @@ spec:
440
409
when it has verified that an "adopted" resource (a resource where the
441
410
ARN annotation was set by the Kubernetes user on the CR) exists and
442
411
matches the supplied CR's Spec field values.
443
-
TODO(vijat@): Find a better strategy for resources that do not have ARN in CreateOutputResponse
0 commit comments