export async function handleContentUpdateByCapiUrl()

in lambda/recipes-responder/src/update_retrievable_processor.ts [43:108]
58 lines of code
13 McCabe index (conditional complexity)

export async function handleContentUpdateByCapiUrl({
	contentType,
	capiUrl,
	internalRevision,
	staticBucketName,
	fastlyApiKey,
	contentPrefix,
	outgoingEventBus,
}: {
	contentType?: ContentType;
	capiUrl: string;
	internalRevision?: number;
	staticBucketName: string;
	fastlyApiKey: string;
	contentPrefix: string;
	outgoingEventBus: string;
}): Promise<number> {
	if (contentType != ContentType.ARTICLE) return 0; //no point processing live-blogs etc.

	// TO FIX UPSTREAM – Crier returns a path that does not include channelled content, giving a 404
	// if the content is not on open. We modify the path manually here to fix. Crier should return a path
	// that is scoped to the appropriate channel if the content is not on open.
	const normalisedCapiUrl = new URL(capiUrl);
	const capiResponse = await retrieveContent(
		`${normalisedCapiUrl.protocol}//${normalisedCapiUrl.hostname}/channel/feast/item${normalisedCapiUrl.pathname}`,
	);

	switch (capiResponse.action) {
		case PollingAction.CONTENT_EXISTS:
			//Great, we have it - but should check if this has now been superceded
			if (
				capiResponse.content?.fields?.internalRevision &&
				internalRevision &&
				capiResponse.content.fields.internalRevision > internalRevision
			) {
				console.log(
					`INFO Retrievable update for ${capiUrl} was superceded - we expected to see ${internalRevision} but got ${capiResponse.content.fields.internalRevision}`,
				);
			} else if (capiResponse.content) {
				return handleContentUpdate({
					content: capiResponse.content,
					staticBucketName,
					fastlyApiKey,
					contentPrefix,
					outgoingEventBus,
				});
			} else {
				console.error(
					`Content for ${capiUrl} existed but was empty, this shouldn't happen :(`,
				);
			}
			return 0;
		case PollingAction.CONTENT_GONE:
		case PollingAction.CONTENT_MISSING:
			//FIXME: should we invoke article-deletion here just in case?
			console.log(
				`INFO Content for ${capiUrl} has gone for this update, assuming that this article was taken down in the meantime.`,
			);
			return 0;
		default:
			//we throw an exception to indicate failure; the lambda runtime will then re-run us and DLQ the message if enough failures happen.
			throw new Error(
				`Could not handle retrievable update from CAPI: PollingAction code was ${capiResponse.action.toString()}. Allowing the lambda runtime to retry or DLQ.`,
			);
	}
}