Releases: aws/aws-rfdk
v1.4.0
Supported CDK Version
Officially Supported Deadline Versions
Features
- aws-rfdk: update Lambda functions to use Node.js 18 (#1224) (f1002cb)
- aws-rfdk: update Lambda functions to use AWS SDK for JavaScript v3 (#1224) (f1002cb)
- deadline: upgraded default Worker instance type to t3.large (#1225) (dfb8536)
Bug Fixes
v1.3.0
Note: Node 14 is End of Life and RFDK >= 1.3.x no longer officially supports it. Node.js 18.0.0 is now
the minimum officially supported version that RFDK now supports. See our documentation on upgrading to RFDK 1.3.
Supported CDK Version
Officially Supported Deadline Versions
Features
Bug Fixes
v1.2.0
Supported CDK Version
Officially Supported Deadline Versions
Bug Fixes
v1.1.0
Supported CDK Version
Officially Supported Deadline Versions
Features
Bug Fixes
- core: add point in time recovery to X509Certificate DynamoDB tables (#883) (89523ba)
- core: fix rate limit errors when deploying cloudwatch log groups (#822) (38df77f)
- deadline: Fix Python bindings of ThinkboxDockerImages (#880) (b283e67)
- deadline: typo in license acceptance error messsage (#898) (f20549e)
- deadline: use new repository installer log path for Deadline 10.2.* (#895) (c6db7c0)
- integ: fix rate limit errors when deploying cloudwatch log groups in integration tests (#827) (fd842b7)
v1.0.0
This release marks the first official stable release of RFDK. All RFDK APIs in this release are considered to be stable and will only be removed through a deprecation process that allows consumers to phase out their usage for at least one minor RFDK version.
NOTE: Future minor RFDK releases may still introduce backwards-incompatible breaking changes. RFDK will continue to announce these breaking changes in this CHANGELOG and on each GitHub release along with documentation and guidance on navigating the change.
Supported CDK Version
Officially Supported Deadline Versions
⚠ BREAKING CHANGES
This change migrates the RFDK to be based on CDK v2. All apps that adopt RFDK 1.x will have to be migrated to CDK v2 as well. To update your app, follow the CDK v2 migration guide.
Additional breaking changes:
- deadline: The
userAwsThinkboxEulaAcceptance
property of theThinkboxDockerImages
construct has been removed and replaced withuserAwsCustomerAgreementAndIpLicenseAcceptance
. The licensing terms of Deadline have been retroactively changed with the
release of Deadline 10.1.23, and these new terms must be agreed to by a code change in your applications.
Features
v0.42.0
Supported CDK Version
Officially Supported Deadline Versions
⚠ BREAKING CHANGES
- deps: The minimum supported version of Node.js has been
changed to Node.js 14
Bug Fixes
v0.41.0
v0.40.0
Supported CDK Version
Officially Supported Deadline Versions
⚠ BREAKING CHANGES
See the
RFDK 0.40.x upgrade documentation
for more details and guidance on addressing these breaking changes.
- The IHealthMonitor and IWorkerFleet interfaces now
extend IConstruct rather than IResource and the stack and env properties
on the HealthMonitor and WorkerInstanceFleet constructs were removed. - deadline: SpotEventPluginFleet now uses EC2 Launch Templates instead of Launch Specifications.
Features
v0.39.0
Supported CDK Version
Officially Supported Deadline Versions
Bug Fixes
v0.38.0
Supported CDK Version
Officially Supported Deadline Versions
⚠ BREAKING CHANGES
RFDK will configure Deadline Secrets Management automatically when using Deadline 10.1.19.x or higher. If your CDK app uses the Repository
construct with an un-pinned VersionQuery
, then upgrading RFDK will set up Deadline Secrets Management. Using Deadline Secrets Management is strongly encouraged for securing Deadline render farms, however it can potentially impact your workflows within Deadline. Please review the Deadline Secrets Management documentation to learn about the feature.
See the RFDK 0.38.x upgrade documentation for more details and guidance on how to upgrade.
Features
- deadline: add Deadline Secrets Management integration in the Render Queue (#528) (48baa18)
- deadline: add Secret Management support for Repository (#514) (8c7dda6)
- deadline: configure identity registration settings for deadline clients (#576) (b9082b2)
- deadline: validate minimum Deadline version for secrets management (#573) (6d5950e)
- examples: add deadline secrets management options to basic example app (#562) (bd31a8d)
- examples: use dedicated subnets in All-In-AWS-Infrastructure-Basic example (#598) (7aaec14)