Matt Davis

So long as the envvar passes all the way through to the actual build environment when the build deps are installed, that's probably good enough for now, but yeah, agreed...

Reopened by request

may be fixed by https://github.com/ansible/ansible/pull/78707?

Sounds like we might just need to make the extended attributes part "best effort", since IIUC there's no definitive and portable way to ensure that the underlying filesystem and security...

This might be easier (or already fixed?) with the handler rewrite stuff @mkrizek has been doing

Paramiko's `SSHClient` added support for `disabled_algorithms` back in their ~2.6 release, which can be manipulated to allow new versions of paramiko to connect to hosts so configured, but the `paramiko_ssh`...

Can you post the relevant output with `-vvv`?

@Thom1729 has it right: absent a user/tag override of this behavior, the built-in loaders will always deserialize a YAML mapping as a Python `dict`, so the behavior you'll see will...

... and yeah, to your original question: *officially* the spec says mapping keys are unordered, though in practice many implementations preserve the input document key order by default. Some relevant...

Yes, Ansible (well, Red Hat) is paying for the VMs in a gigantic Azure VMSS that serves both ansible-core and the community collections projects, among other things.