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
Fix CICD Pipeline: Upgrade Ubuntu version on Azure DevOps agent, Go dependency errors, and more (#421)
* Upgrade Ubuntu version on Azure DevOps agent
* Update CHANGELOG.md
* Run go mod tidy before installing linting tools
* Upgrade to Go version 1.17
* chore: require terraform version to be 0.12.31 or latest 0.12.x
* Publish new version when updating lambda code
Co-authored-by: jrsholly <[email protected]>
Co-authored-by: Hart <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+23-11
Original file line number
Diff line number
Diff line change
@@ -1,27 +1,41 @@
1
+
## next
2
+
3
+
- Upgrade to Go version 1.17
4
+
- Upgrade Ubuntu version on Azure DevOps Agent
5
+
- Fix Go dependency errors in pipeline
6
+
- Require at least `0.12.31` or later `0.12.x` versions of Terraform to recieve new provider updates
7
+
1
8
## v0.33.8
9
+
2
10
- Upgrade the Swagger UI dependency to remove a very dangerous vulnerability (upgrade Swagger UI to v3.51.2).
3
11
4
12
## v0.33.7
13
+
5
14
- Update requirements packages for docs.
6
15
- Update gotool version for pipeline.
7
16
8
17
## v0.33.6
18
+
9
19
- Add LakeFormation to the principal IAM policy.
10
20
- Update mocks
11
21
- updates requirements packages for docs
12
22
13
23
## v0.33.5
24
+
14
25
- rename pipeline credentials inputs
15
26
16
27
## v0.33.4
28
+
17
29
- Upgrade aws provider to v2.65.0 to fix SES configuration set. [terraform-provider-aws #12024](https://github.com/hashicorp/terraform-provider-aws/pull/12024)
18
30
- Add firewall manager to principal IAM policy.
19
31
20
32
## v0.33.3
33
+
21
34
- Remove apigatewayv2 from the principal IAM policy.
22
35
- Update to the principal IAM policy name lex-models.
23
36
24
37
## v0.33.2
38
+
25
39
- Add to the principal IAM policy:
26
40
- apigatewayv2
27
41
- comprehend
@@ -32,28 +46,34 @@
32
46
- wafv2
33
47
34
48
## v0.33.1
49
+
35
50
- Fix populate reset queue when dynamodb returns paginated result
36
51
- Add account status to last evaluated key when querying account table using global secondary index
37
52
- Fix gosec issue related to G601 (CWE-118): Implicit memory aliasing in for loop
38
53
39
54
## v0.33.0
55
+
40
56
- Upgrade aws-nuke to v1.3.0
41
57
42
58
## v0.32.0
59
+
43
60
- Upgrade go to 1.15
44
61
- Upgrade go mod dependencies version.
45
62
- Improved test scenarios.
46
63
- Add `iotanalytics:*` policy to the set of allowed services.
47
64
- Increase timeout for functional test execution.
48
65
49
66
## v0.31.3
67
+
50
68
- Fix data and update visualization for codebuild reset widget and error scrappers.
51
69
52
70
## v0.31.2
53
-
- Fix bug: Status change in account table fails for leased accounts that are expired. See https://github.com/Optum/dce/issues/344
71
+
72
+
- Fix bug: Status change in account table fails for leased accounts that are expired. See <https://github.com/Optum/dce/issues/344>
54
73
- Fix bug: When lease starts today, fixed usage start and end date that was printed in log message.
55
74
56
75
## v0.30.1
76
+
57
77
- Added new tool in `tools` folder for generating Markdown and IAM example policy for AWS Nuke
58
78
support. See README in `tools/awsnukedocgen`.
59
79
- Added new services supported by DCE: Kinesis Analytics, Kinesis Video, Opsworks CM, Robomaker,
@@ -182,7 +202,6 @@ This release also removes the deprecated DynamoDB tables with "Redbox" prefixes.
182
202
- RedboxLeaseProd --> Leases
183
203
- UsageCache --> Usage
184
204
185
-
186
205
**Migration Notes**
187
206
188
207
_DynamoDB Migration_
@@ -195,7 +214,6 @@ To do this, you may run the migration script in [/scripts/migrations/v0.21.0_ren
195
214
196
215
Note that this release does ***not*** delete the old tables, to provide the opportunity to migrate data. Subsequent releases _will_ destroy the old tables.
197
216
198
-
199
217
## v0.20.0
200
218
201
219
- Fixed a bug in a migration script
@@ -210,12 +228,10 @@ Note that this release does ***not*** delete the old tables, to provide the oppo
210
228
- Fixed issue with the lease check logic that was expiring non-expired leases.
211
229
- Migration script to fix wrongly expired leases
212
230
213
-
214
231
## v0.19.1
215
232
216
233
- Fixed issue with lease status reason not being set when the lease was newly created.
217
234
218
-
219
235
## v0.19.0
220
236
221
237
**BREAKING CHANGES**
@@ -232,7 +248,6 @@ _Other Changes_
232
248
- Refactored lease API controller and methods to organize methods into files.
233
249
- Add functions to evaluate who is calling an API and what their role is
234
250
235
-
236
251
### Migration Notes for v0.19.0
237
252
238
253
In order to upgrade your DCE deployment to v0.19.0, you will need to:
@@ -244,7 +259,6 @@ In order to upgrade your DCE deployment to v0.19.0, you will need to:
244
259
- Marks all `*Locked` leases as `Inactive`
245
260
- Update any DCE API clients to include the `expiresOn` property in their `Lease` record.
246
261
247
-
248
262
### _Expiring Leases Model_
249
263
250
264
Prior to v0.19.0, leases were held in perpetuity by principals, or until the principal removed their lease via the `DELETE /leases` endpoint. Leased accounts would be "reset" at the end of the week. During reset, the lease would be marked as _Locked_, and then marked as _Active_ again after the reset was complete.
@@ -256,8 +270,8 @@ Changes for this new behavior include:
256
270
- Simplified lease status model to include only two statuses: Inactive and Active.
257
271
- Changed check_budget to update_lease_status and added check for expiration date.
258
272
- Changed SQS and SNS notifications for lease status change to be triggered by lease status change in DB.
0 commit comments