community.general/test/integration/targets/shadowed_module/runme.sh

#!/usr/bin/env bash

set -ux

OUT=$(ansible-playbook playbook.yml -i inventory -e @../../integration_config.yml "$@" 2>&1 | grep 'ERROR! Module "tags" shadows the name of a reserved keyword.')

if [[ -z "$OUT" ]]; then
    echo "Fake tags module did not cause error"
    exit 1
fi

# This playbook calls a lookup which shadows a keyword.
# This is an ok situation, and should not error
ansible-playbook playbook_lookup.yml -i ../../inventory -e @../../integration_config.yml "$@"
Error if a module is found to shadow a reserved keyword (#34649) * Error if a module is found to shadow a reserved keyword * Add test for shadowed module * Bring in functools.wraps for the decorator * Drop the decorator, make _find_plugin the real function, find_plugin now holds the shadow logic * Swap order of functions for bottom to top execution order * Only error for modules * Add test for loading a lookup plugin that shadows a keyword 2018-04-10 16:26:27 +02:00			`#!/usr/bin/env bash`

			`set -ux`

			`OUT=$(ansible-playbook playbook.yml -i inventory -e @../../integration_config.yml "$@" 2>&1 \| grep 'ERROR! Module "tags" shadows the name of a reserved keyword.')`

			`if [[ -z "$OUT" ]]; then`
			`echo "Fake tags module did not cause error"`
			`exit 1`
			`fi`

			`# This playbook calls a lookup which shadows a keyword.`
			`# This is an ok situation, and should not error`
Use relative inventory paths instead of symlinks. 2019-01-08 02:54:11 +01:00			`ansible-playbook playbook_lookup.yml -i ../../inventory -e @../../integration_config.yml "$@"`