argument_spec: default value for dict entries do not work about ansible HOT 9 CLOSED

Files identified in the description:

• bin/ansible

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

from ansible.

Duplicate of #83268 #78889

from ansible.

Duplicate of #83268 #78889

hmmm not sure.

This is about default values for keys within dicts. Take a look at the sample config above. Looking at the issues you cited they seem to have different data structures ...

from ansible.

default is just for documentation and the existing type validators only guarantee that it can be converted to the type, not that it is actually that type.

... because of complexities with variable precedence. At the moment, we could return the validated and coerced variables in an ansible_facts key from the validate_argument_spec action plugin, but this would break the assumptions of variable precedence. At this time we do not have plans on implementing a feature that would allow re-injecting the validated and coerced variables.

from ansible.

Duplicate of #80298 #80604

from ansible.

:-( ok

from ansible.

What seems odd, is that when you are setting required: true and default: xxx then ansible will complain, that a default value and required would not go together. If default is for documentation only, then this error makes little sense.

from ansible.

closing as per above

from ansible.

the error is correct, the documentation should not specify a default if the argument is required, it is not only code consistency we check for.

from ansible.