Create a Construct to supply Deadline installers

[horsmand]

We would like a construct which determines the S3 URI's for the Deadline installers and Deadline Docker recipes. The version of Deadline for these can be either specified by the user or defaulted to the latest version.

For now, this will be integrated with the Repository construct to get the repository installer for it to use. In the future we can extend it out to be used by other constructs that require Deadline installers or the Docker recipes as well.

Use Case

Currently to get the repository installer, we use hard-coded values that make assumptions about where the installer should be found in S3:

aws-rfdk/packages/aws-rfdk/lib/deadline/lib/version.ts

Lines 293 to 310 in 75d0f9f

	const installerBucket = Bucket.fromBucketName(this, 'ThinkboxInstallers', ExactVersion.INSTALLER_BUCKET);
	const { majorVersion, minorVersion, releaseVersion, patchVersion } = versionComponents;
	this.majorVersion = majorVersion;
	this.minorVersion = minorVersion;
	this.releaseVersion = releaseVersion;
	const fullVersionString = this.fullVersionString(patchVersion);
	const objectKey = `Deadline/${fullVersionString}/Linux/DeadlineRepository-${fullVersionString}-linux-x64-installer.run`;
	this.linuxInstallers = {
	patchVersion,
	repository: {
	s3Bucket: installerBucket,
	objectKey,
	},
	};

This would provide a more robust way of determining the installer locations

Proposed Solution

A VersionQuery Construct that contains a CustomResource that downloads the version index file and parses it, then returns the required information about the installers for a specific Deadline version.

The Repository construct will then take the versioned installers supplied by the VersionQuery construct, and use the repo installer.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[zxkane]

Any plan to mirror the deadline installers to other aws partitions?

[jusiskin]

@zxkane - Thanks for reaching out! I've taken your feature request and made a separate issue (#207).