As a user I want to be able to pass a path to a YAML file with a list of Ansible Collections I wish to be represented by a Ansible Remote in the Ansible plugin

[ajsween]

When creating or updating a remote Collection for the Ansible plugin the REST API documents a parameter, "requirements_file." This parameter is currently exposed via the pulp CLI tool. However, it only accepts a string directly. When you instead pass a file path to a YAML file it fails to serialize the YAML file correctly to JSON and throws an exception. My YAML file looked similar to the following:

---
collections:
  - testing.ansible_testing_content
  - pulp.squeezer

[ajsween]

In examining the behavior of the wrapper today, I think this may actually be a bug. It appears to me that a file path is accepted but that serialization is not successful.

[mdellweg]

That is debatable. I'm pretty sure, JSON as a format is accepted, so adding YAML would be a feature.
Agreed, this may look weird when coming from an ansible minted mindset.
The change i envision to solve this would allow YAML anywhere in place of only JSON. And to me that is a feature.

[daviddavis]

@mdellweg I believe that the REST API actually expects yaml for requirements_file. See https://docs.pulpproject.org/pulp_ansible/restapi.html#operation/remotes_ansible_collection_create.

[mdellweg]

So it's a feature request to accept yaml where we already accept json, and a bug by the principle of least surprise?