requirements pyyaml < 6 is cumbersome and conflicts with other tools like ansible

[dch]

In local testing, I found no issues using pyyaml = 6.0 for OCI. Is it possible
to bump to 6.0 please?

This avoids conflicting with other common tools such as Ansible which requires
a more recent py-yaml than > 2 years old ( https://github.com/yaml/pyyaml/tags )

AFAICT the major change for pyyaml 6.0+ is dropping support of python2.7 which
is over a decade EOL now.

[dch]

FWIW I've been using this without issue on FreeBSD for a couple of weeks now, wouldbe a great change to get into src.

[josephholsten]

Found this patch: https://cgit.freebsd.org/ports/commit/?id=af75775bb587e2e801b8aea4fbf62d02fee27d8e

@anup-21 @harshitkumar017 @mandyht Is there a documented reason we’re still keeping this? We’re saying we stopped supporting 2.x on 2021-08-01 at https://docs.oracle.com/en-us/iaas/Content/API/Concepts/cliconcepts.htm.

I know we’re not committing to FreeBSD support, but we do have them in the image marketplace and have a partner talking it up at https://amperecomputing.com/blogs/getting-cloud-native-with-freebsd-on-oci-ampere-a1-with-terraform-, I’d really like us not to have them patching us.

[mandyht]

Created a task to investigate this. Thanks @dch and @josephholsten for sharing.

[mandyht]

Next week's release of v3.27.1 will include the upper bound change to less than or equal to 6. This should resolve the original issue.