ansible/test/integration/targets/no_log/secretvars.yml

# These values are in a separate vars file and referenced dynamically to avoid spurious counts from contextual error messages
# that show the playbook contents inline (since unencrypted playbook contents are not considered secret).
log_me_prefix: LOG_ME_

# Unique values are used for each secret below to ensure that one secret "learned" does not cause another non-secret
# value to be considered secret simply because they share the same value. A common substring is, however, present in
# each one to simplify searching for secret values in test output. Having a unique value for each also helps in
# debugging when unexpected output is encountered.

# secrets for no_log_suboptions.yml
s101: SECRET101
s102: SECRET102
s103: SECRET103
s104: SECRET104
s105: SECRET105
s106: SECRET106
s107: SECRET107

# secrets for no_log_suboptions_invalid.yml
s201: SECRET201
s202: SECRET202
s203: SECRET203
s204: SECRET204
s205: SECRET205
s206: SECRET206
s207: SECRET207
s208: SECRET208
s209: SECRET209
s210: SECRET210
s211: SECRET211
s212: SECRET212
s213: SECRET213
Preserve `_ansible_no_log` from action result; fix `include_vars` to set properly (#84143) * fixes for CVE-2024-8775 * propagate truthy `_ansible_no_log` in action result (previously superseded by task-calculated value) * always mask entire `include_vars` action result if any file loaded had a false `show_content` flag (previously used only the flag value from the last file loaded) * update no_log tests for CVE-2024-8775 * include validation of _ansible_no_log preservation when set by actions * replace static values with dynamic for increased robustness to logging/display/callback changes (but still using grep counts :( ) * changelog * use ternary, coerce to bool explicitly 1 month ago			`# These values are in a separate vars file and referenced dynamically to avoid spurious counts from contextual error messages`
			`# that show the playbook contents inline (since unencrypted playbook contents are not considered secret).`
			`log_me_prefix: LOG_ME_`

			`# Unique values are used for each secret below to ensure that one secret "learned" does not cause another non-secret`
			`# value to be considered secret simply because they share the same value. A common substring is, however, present in`
			`# each one to simplify searching for secret values in test output. Having a unique value for each also helps in`
			`# debugging when unexpected output is encountered.`

			`# secrets for no_log_suboptions.yml`
			`s101: SECRET101`
			`s102: SECRET102`
			`s103: SECRET103`
			`s104: SECRET104`
			`s105: SECRET105`
			`s106: SECRET106`
			`s107: SECRET107`

			`# secrets for no_log_suboptions_invalid.yml`
			`s201: SECRET201`
			`s202: SECRET202`
			`s203: SECRET203`
			`s204: SECRET204`
			`s205: SECRET205`
			`s206: SECRET206`
			`s207: SECRET207`
			`s208: SECRET208`
			`s209: SECRET209`
			`s210: SECRET210`
			`s211: SECRET211`
			`s212: SECRET212`
			`s213: SECRET213`