ansible/test/integration
Dag Wieers 2ef0946370
Warn on incorrect use of parameter, and remove fix for now (#54336)
* Fix wrong example, remove strictness and fix tests

It was obvious that (because of an incorrect example) people were using
the **xml** module incorrectly, specifying the `attribute` parameter
where it was not supported (i.e. ignored).

While this functionality would have been useful, it currently returns as
if the information was requested from the parent, so we cannot simply
make it to what would be expected.

Therefor the real solution is to provide a warning when we find
incorrect use, and deprecate this use. Then later we could implement
this functionality correctly.

While troubleshooting this issue, I found that in some cases our
integration tests were not being run when we expected it.

This fixes #53459

* Change warning

* Fix weird sanity test error

* Add a comment to the deprecate-test
2019-03-29 15:13:19 +01:00
..
host_vars
targets Warn on incorrect use of parameter, and remove fix for now (#54336) 2019-03-29 15:13:19 +01:00
cloud-config-aws.ini.template
cloud-config-azure.ini.template
cloud-config-cloudscale.ini.template
cloud-config-cs.ini.template
cloud-config-gcp.ini.template
cloud-config-gitlab.ini.template
cloud-config-hcloud.ini.template Add hcloud server module (#53062) 2019-03-05 07:30:24 +01:00
cloud-config-opennebula.ini.template
cloud-config-openshift.kubeconfig.template
cloud-config-tower.ini.template
cloud-config-vultr.ini.template
integration.cfg Force tests to set ansible_python_interpreter. (#54191) 2019-03-21 21:54:41 -07:00
integration_config.yml
inventory Overhaul ansible-test code coverage and injector. (#53510) 2019-03-13 07:14:12 -07:00
inventory.networking.template
inventory.remote.template
inventory.winrm.template
network-integration.cfg
target-prefixes.network
windows-integration.cfg