Sloane Hertel
Sloane Hertel
You need to specify `elements` with `type: list`: ```yaml argument_specs: main: short_description: validation for params in tasks/main.yml options: cron_jobs: type: "list" required: true elements: "dict" options: xxx: type: "str" required:...
I am unable to reproduce, and the example given `https://git.example.com/scm/ag/ansible.utils.git` does not exist - please provide a full reproducer. The errors suggests that the metadata in the git repo is...
I was able to reproduce on devel. This occurs only if the collection is already installed (a temporary workaround would be to use --force or --force-with-deps).
@jamesosbourn If you omit the `name` from your requirements file, that should also work around the issue (and is why none of the tests are hitting the issue).
The only requirements which are allowed to use non-semver versions are `type: git`. The version must be a commitish object, for example a tag. The collection inside the git repo...
@nitzmahone Not sure if you have any thoughts on this, but after thinking about this in conjunction with module_defaults, I'm wondering if the `resolved_action` attribute is just rather unhelpful for...
I didn't actually realize this also fixes https://github.com/ansible/ansible/issues/81905, but it does so I added tests and a changelog.