Provide deprecation warnings on return values/facts

[nitzmahone]

SUMMARY

Allow modules and actions to tag attributes of return values (including facts) as deprecated. Preserve the tagging within the controller and variable store, and only fire a deprecation warning when a tagged attribute is "touched" by a user-initiated event (usually templating).

This is prerequisite for the ultimate fix to #43798 (deprecating usage of all un-namespaced facts and eventually changing the default to namespaced-only).

Depends on #80747

ISSUE TYPE

• Feature Idea

COMPONENT NAME

AnsibleUnsafe

ADDITIONAL INFORMATION

Refactor AnsibleUnsafe to a new class that supports multiple types of tagging, and ensure that the various tagged data is always preserved if attempting to add a new tag. Trigger the warning when encountering a tagged value during templating.

[ansibot]

Files identified in the description:

• lib/ansible/modules/files/template.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibot]

Files identified in the description:
None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[samdoran]

Is this a feature we would still like to add, maybe in 2.11? Sounds like this may be on the potential 2.11 roadmap.

[nitzmahone]

Yep, it sounds like @relrod wants to run with the generic tagging proxy, so we'll be writing it up Real Soon Now