Function executeCommand

packages/lambda/src/cli/index.ts:176–304

(
	args: string[],
	remotionRoot: string,
	logLevel: LogLevel,
	_providerSpecifics: ProviderSpecifics<AwsProvider> | null,
	fullClientSpecifics: FullClientSpecifics<AwsProvider> | null,
)

};

export const executeCommand = async (
	args: string[],
	remotionRoot: string,
	logLevel: LogLevel,
	_providerSpecifics: ProviderSpecifics<AwsProvider> | null,
	fullClientSpecifics: FullClientSpecifics<AwsProvider> | null,
) => {
	try {
		const providerSpecifics =
			_providerSpecifics ?? LambdaClientInternals.awsImplementation;
		await matchCommand({
			args,
			remotionRoot,
			logLevel,
			providerSpecifics: providerSpecifics,
			fullClientSpecifics: fullClientSpecifics ?? awsFullClientSpecifics,
		});
	} catch (err) {
		const error = err as Error;
		if (
			error.message.includes(
				'The role defined for the function cannot be assumed by Lambda',
			)
		) {
			if (parsedLambdaCli['custom-role-arn']) {
				Log.error(
					{indent: false, logLevel},
					`
	The role "${parsedLambdaCli['custom-role-arn']}" does not exist or has the wrong policy assigned to it. Do either:
	- Remove the "--custom-role-arn" parameter and set up Remotion Lambda according to the setup guide
	- Make sure the role has the same policy assigned as the one returned by "npx ${BINARY_NAME} ${POLICIES_COMMAND} ${ROLE_SUBCOMMAND}"
	
	Revisit ${DOCS_URL}/docs/lambda/setup and make sure you set up the role and role policy correctly. Also see the troubleshooting page: ${DOCS_URL}/docs/lambda/troubleshooting/permissions. The original error message is:
	`.trim(),
				);
			}

			Log.error(
				{indent: false, logLevel},
				`
The role "${ROLE_NAME}" does not exist in your AWS account or has the wrong policy assigned to it. Common reasons:
- The name of the role is not "${ROLE_NAME}"
- The policy is not exactly as specified in the setup guide

Revisit ${DOCS_URL}/docs/lambda/setup and make sure you set up the role and role policy correctly. Also see the troubleshooting page: ${DOCS_URL}/docs/lambda/troubleshooting/permissions. The original error message is:
`.trim(),
			);
		}

		if (error.stack?.includes('AccessDenied')) {
			Log.error(
				{indent: false, logLevel},
				`
AWS returned an "AccessDenied" error message meaning a permission is missing. Read the permissions troubleshooting page: ${DOCS_URL}/docs/lambda/troubleshooting/permissions. The original error message is:
`.trim(),
			);
		}