systemd-stable/test/test-execute/exec-passenvironment-repeated.service

# SPDX-License-Identifier: LGPL-2.1-or-later
[Unit]
Description=Test for PassEnvironment with a variable name repeated

[Service]
ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$VAR4" = "new\nline" && test "$$VAR5" = passwordwithbackslashes'
Type=oneshot
PassEnvironment=VAR1 VAR2
PassEnvironment=VAR1 VAR3
PassEnvironment=VAR1 VAR4
PassEnvironment=VAR1 VAR5
tests: add spdx license header to test unit/link/network/conf files Those are all consumed by our parser, so they all support comments. I was considering whether they should have a license header at all, but in the end I decided to add it because those files are often created by copying parts of real unit files. And if the real ones have a license, then those might as well. It's easier to add it than to make an exception. 2021-10-17 19:07:22 +03:00			`# SPDX-License-Identifier: LGPL-2.1-or-later`
test-execute: Add tests for new PassEnvironment= directive Check the base case, plus erasing the list, listing the same variable name more than once and when variables are absent from the manager execution environment. Confirmed that `sudo ./test-execute` passes and that modifying the test cases (or the values of the set variables in test-execute.c) is enough to make the test cases fail. 2015-11-08 21:37:05 +03:00			`[Unit]`
			`Description=Test for PassEnvironment with a variable name repeated`

			`[Service]`
test: add testcase for environment file variables with backslashes systemd silently strips out backslashes in variables from environment files. Add a testcase that explicitly tests for this behaviour. 2018-05-10 16:28:10 +03:00			`ExecStart=/bin/sh -x -c 'test "$$VAR1" = "word1 word2" && test "$$VAR2" = word3 && test "$$VAR3" = "\\$$word 5 6" && test "$$VAR4" = "new\nline" && test "$$VAR5" = passwordwithbackslashes'`
test-execute: Add tests for new PassEnvironment= directive Check the base case, plus erasing the list, listing the same variable name more than once and when variables are absent from the manager execution environment. Confirmed that `sudo ./test-execute` passes and that modifying the test cases (or the values of the set variables in test-execute.c) is enough to make the test cases fail. 2015-11-08 21:37:05 +03:00			`Type=oneshot`
			`PassEnvironment=VAR1 VAR2`
			`PassEnvironment=VAR1 VAR3`
test-execute: Introduce tests for environment values containing newlines Also fix one case where the presence of a newline was used to generate an invalid environment assignment. Tested: with mkosi, which builds the local tree and run ninja tests. 2018-03-17 02:30:42 +03:00			`PassEnvironment=VAR1 VAR4`
test: add testcase for environment file variables with backslashes systemd silently strips out backslashes in variables from environment files. Add a testcase that explicitly tests for this behaviour. 2018-05-10 16:28:10 +03:00			`PassEnvironment=VAR1 VAR5`