Klaas Demter

Hi, I think you're supposed to use azure-cli 2.64.0 with collection currently https://github.com/ansible-collections/azure/blob/4a656c6f8151fca3f6a914a25cbb6601c28eaea2/requirements.txt#L5

you're saying the same thing as we are @rnowagk -- what we're saying is downgrade to use what azure collection currently expects, what you're saying is upgrade azure collection requirements...

List of available backups is coming from here: https://learn.microsoft.com/en-us/rest/api/backup/recovery-points/list?view=rest-backup-2024-04-01&tabs=Python#code-try-0

Workaround using azure_rm_deployment (not idempotent): ``` - name: Create Data Collection Rule Association for new VM azure.azcollection.azure_rm_deployment: resource_group: "{{ resource_group_name }}" name: "{{ inventory_hostname_short }}_data_collection_rule_association" location: westus template: $schema: "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#"...

Crosslinking #3829 and #35417

I think you can make it easier by setting: `/var/lib/rancher/k3s/agent/containerd /var/lib/containerd` So the context will simply follow whatever your selinux rules for the standard containerd path are.

this should also be a problem for aap, because you have to pay per host :)

I am unsure if it's actually considered a problem, I guess for now it is by design :)

I think this is https://github.com/k3s-io/k3s-selinux/issues/34 -- see https://github.com/k3s-io/k3s-selinux/issues/34#issuecomment-1612657550 on how to set it correctly

Can we do something like this: ``` else: try: key = next(iter(old[0])) new = sorted(new, key=lambda x: x.get(key, None)) old = sorted(old, key=lambda x: x.get(key, None)) except TypeError: for i...