Allowing Quarto to execute and read shell scripts passed to the post-/pre-render option automatically

[arnaudgallou]

Description

Not a Quarto problem per se but is there a way to give Quarto default execute and read permissions to shell scripts passed to the pre-/post-render option (assuming it's safe to do)?

Currently, using pre-render: myscript.sh throws a permission denied error. I need to give explicit execute and read permission before being able to use pre-rendered shell scripts, which isn't very convenient.

[mcanouil]

I need to give explicit execute and read permission before being able to use pre-rendered shell scripts, which isn't very convenient.

I would argue that this avoid Quarto to run code you didn't want to be executed without having you to explicitly state it should using the permissions.

[arnaudgallou]

That's true but to be honest that should also apply to any script.

[cderv]

is there a way to give Quarto default execute and read permissions to shell scripts passed to the pre-/post-render option (assuming it's safe to do)?

I am not even sure this is possible to do so. If you are not using one of the script specifically supported Typescript (run with deno), Python, R or Lua, Quarto will just pass the command as-is

quarto-cli/src/command/render/project.ts

Lines 997 to 1007 in e4a8898

	const result = await execProcess({
	cmd: args,
	cwd: projDir,
	stdout: quiet ? "piped" : "inherit",
	env,
	});
	if (!result.success) {
	throw new Error();
	}
	}
	}

So in your case args is myscript.sh directly, and this is then expected to be executable. On linux bash, if you try to do myscript.sh, you need to make it executable. Otherwise, you need to call the script differently.
So set pre-render to another command that allow to run your script another way, which does not require executable script. Like on linux bash script.sh or on windows pwsh script.ps1.

Did you try that ?

[arnaudgallou]

So in your case args is myscript.sh directly, and this is then expected to be executable.

That makes sense and I confirm that using bash script.sh works.

[cscheid]

I agree that this isn't convenient, but good text editors will let you automatically set the +x flag on scripts :)

[arnaudgallou]

Thanks for the tip.