Files
community.general/test/integration/targets
John R Barker a23c95023b Module deprecation: docs, scheme and tests (#34100)
Enforce module deprecation.
After module has reached the end of it's deprecation cycle we will replace it with a docs stub.

* Replace deprecated modules with docs-only sub
* Use of deprecated past deprecation cycle gives meaningful message (see examples below)
* Enforce documentation.deprecation dict via `schema.py`
* Update `ansible-doc` and web docs to display documentation.deprecation
* Document that structure in `dev_guide`
* Ensure that all modules starting with `_` have a `deprecation:` block
* Ensure `deprecation:` block is only used on modules that start with `_`
* `removed_in` A string which represents when this module needs **deleting**
* CHANGELOG.md and porting_guide_2.5.rst list removed modules as well as alternatives
* CHANGELOG.md links to porting guide index

To ensure that meaningful messages are given to the user if they try to use a module at the end of it's deprecation cycle we enforce the module to contain:
```python
if __name__ == '__main__':
    removed_module()
```
2018-01-30 12:23:52 +00:00
..
2017-08-31 12:11:43 -07:00
2018-01-16 17:47:58 -05:00
2018-01-29 11:49:30 +01:00
2017-12-15 14:40:02 -05:00
2017-09-14 07:14:30 -07:00
2018-01-19 17:14:32 -05:00
2017-08-15 23:12:08 -07:00
2017-07-28 10:57:16 -07:00
2018-01-10 10:52:26 +05:30
2018-01-17 10:14:20 +05:30
2018-01-22 11:30:52 +05:30
2017-08-31 12:11:43 -07:00
2018-01-15 21:15:04 -08:00
2017-09-14 07:14:30 -07:00
2017-12-21 21:30:10 +01:00
2017-08-31 12:11:43 -07:00
2018-01-24 10:22:04 -08:00
2017-08-31 12:11:43 -07:00
2018-01-27 12:35:18 +01:00
2018-01-03 12:20:43 -08:00