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

• 2.114.1

Officially Supported Deadline Versions

• 10.1.9.2 to 10.3.1.4

Features

• deadline: DocumentDB engine version support upgraded upto version 5.0 (#1155) (7905f91)

Bug Fixes

• add usage-based licensing ports for new Cinema4d versions (#1142) (213605d)

v1.2.0

Supported CDK Version

• 2.70.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.2.1.0

Bug Fixes

• update Deadline version to 10.2 in the SEP example (#1021) (d5b8c62)

v1.1.0

Supported CDK Version

• 2.54.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.2.0.10

Features

• deadline: allow minor version upgrades in Repository construct (#896) (9e0b7e0)

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

• 2.33.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.23.6

⚠ 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 the ThinkboxDockerImages construct has been removed and replaced with userAwsCustomerAgreementAndIpLicenseAcceptance. 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

• all: migrate to CDKv2 (#738) (7c06857)
• deadline: adds UserData property to WorkerInstanceFleet (#781) (b7e48b0)
• deadline: update to Deadline licensing terms (#742) (03bc8ee)

v0.42.0

Supported CDK Version

• 1.160.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.21.4

⚠ BREAKING CHANGES

• deps: The minimum supported version of Node.js has been
  changed to Node.js 14

Bug Fixes

• lambda-layers: add ap-southeast-3 to region deny list (#685) (6806951)

v0.41.0

Supported CDK Version

• 1.149.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.20.3

v0.40.0

Supported CDK Version

• 1.137.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.20.2

⚠ 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

• deadline: change SEP construct to use launch templates instead of launch specifications (#513) (7c61c18)

v0.39.0

Supported CDK Version

• 1.129.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.19.4

Bug Fixes

• deadline: change dependency when configuring repository clients to its auto scaling group (#626) (6464f40)
• deadline: configure identity registration settings using RenderQueue backend security group (#633) (35bb326), closes #632

v0.38.0

Supported CDK Version

• 1.129.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.19.4

⚠ 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)

Bug Fixes

• deadline: allow traffic from RenderQueue to UsageBasedLicensing (#617) (dfbf88f)
• deadline: fix issue in client TLS configuration for Deadline 10.1.18 (#543) (05b14f9)
• deadline: reinstall repository even if version is not changed (821bab2)

v0.37.0

Supported CDK Version

• 1.116.0

Officially Supported Deadline Versions

• 10.1.9.2 to 10.1.17.4

⚠ BREAKING CHANGES

• deadline: MountableEfs will not work with the Repository construct when
  created with an imported EFS Access Point
• deadline: Farms currently not configured to use external TLS on
  the Render Queue will be modified to have it enabled and using the
  default certificate and hosted zone. To keep external TLS disabled, the
  enabled flag on the RenderQueueExternalTLSProps can be set to false;
  however, we strongly encourage you to enable TLS. See theRFDK 0.37.x upgrade documentation
  for more details and guidance on how to upgrade.

Features

• core: add FSx for Lustre integration (#461) (bf5bbb9)
• deadline: use TLS between RenderQueue and clients by default (#491) (1e3eb63), closes #490

Documentation

• add construct architecture diagrams (#508) (b83c0e0)