Skip to content

Commit 8f50903

Browse files
committed
Update changelog
1 parent 227648d commit 8f50903

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

CHANGELOG.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
1+
## v0.33.9
2+
- Allow account reset codebuild access to custom nuke config bucket
3+
14
## v0.33.8
25
- Upgrade the Swagger UI dependency to remove a very dangerous vulnerability (upgrade Swagger UI to v3.51.2).
36

@@ -103,7 +106,7 @@
103106

104107
This release makes breaking changes to the `GET /leases` endpoint, so that requests will always return a HTTP 200 response, with a JSON array in the payload, even if the result set is empty. Previously, if a query had no results, the endpoint would return an HTTP 404 response, with an error object in the response body.
105108

106-
DCE API clients will need to be updated accordingly, to handle this response.
109+
DCE API clients will need to be updated accordingly, to handle this response.
107110

108111
## v0.25.0
109112

@@ -249,7 +252,7 @@ In order to upgrade your DCE deployment to v0.19.0, you will need to:
249252

250253
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.
251254

252-
As of v0.19.0, leases are held for a defined time period (defined by the `expiresOn` property), and then destroyed (marked as `Inactive`). Accounts are reset after the leases expires. There is no longer any type of `*Locked` state, as leases are always either `Active` or `Inactive`.
255+
As of v0.19.0, leases are held for a defined time period (defined by the `expiresOn` property), and then destroyed (marked as `Inactive`). Accounts are reset after the leases expires. There is no longer any type of `*Locked` state, as leases are always either `Active` or `Inactive`.
253256

254257
Changes for this new behavior include:
255258

@@ -304,7 +307,7 @@ Changes for this new behavior include:
304307
## v0.13.0
305308

306309
- **BREAKING** Remove Optum-specific rules from the default aws-nuke config.
307-
- **BREAKING** Disable `aws-nuke` by default.
310+
- **BREAKING** Disable `aws-nuke` by default.
308311
- Add outputs for DynDB table ARNs
309312

310313
**v0.13.0 Migration Notes**

0 commit comments

Comments
 (0)