Where is the ansible-inventory.yaml ?

[squeeb]

Based on https://lima-vm.io/docs/dev/internals/#instance-directory-lima_homeinstance , an ansible-inventory.yaml should appear in ${LIMA_HOME}/<INSTANCE> once the instance has been brought up.

This is not the case:

user@mac ~/.lima/debian-12 $ ls -la
total 3157592
drwx------@ 20 user  staff           640  4 Jun 16:43 .
drwx------@  4 user  staff           128  4 Jun 16:42 ..
-rw-r--r--@  1 user  staff     337903616  4 Jun 16:42 basedisk
-rw-r--r--@  1 user  staff        133120  4 Jun 16:43 cidata.iso
-r--r--r--@  1 user  staff           379  4 Jun 16:43 cloud-config.yaml
srwxr-xr-x@  1 user  staff             0  4 Jun 16:43 default_ep.sock
srwxr-xr-x@  1 user  staff             0  4 Jun 16:43 default_fd.sock
-rw-------@  1 user  staff  107374182400  4 Jun 16:52 diffdisk
-rw-r--r--@  1 user  staff             6  4 Jun 16:43 ha.pid
srwxr-xr-x@  1 user  staff             0  4 Jun 16:43 ha.sock
-rw-r--r--@  1 user  staff          6661  4 Jun 16:53 ha.stderr.log
-rw-r--r--@  1 user  staff           167  4 Jun 16:43 ha.stdout.log
-r--r--r--@  1 user  staff             5  4 Jun 16:42 lima-version
-rw-r--r--@  1 user  staff          1653  4 Jun 16:42 lima.yaml
-rw-------@  1 user  staff             0  4 Jun 16:43 serialv.log
-rw-------@  1 user  staff           684  4 Jun 16:43 ssh.config
srw-------@  1 user  staff             0  4 Jun 16:43 ssh.sock
-rw-------@  1 user  staff        131072  4 Jun 16:43 vz-efi
-rw-r--r--@  1 user  staff            70  4 Jun 16:42 vz-identifier
-rw-r--r--@  1 user  staff             6  4 Jun 16:43 vz.pid

I want to be able to dynamically include this file during ansible playbook development for local development.

[afbjorklund]

We deprecated the ansible provisioning and the ansible-inventory.yaml, but haven't yet fully removed it from the code...

The file was only generated during the playbook execution, so it is not created upon instance creation (as you noticed).

• Deprecate the ansible provision playbook #3450

Now that the ssh.config is generated, it is easy to generate an inventory consisting of only the "lima-default" (etc) aliases:

lima:
  hosts:
    lima-default:

$ ansible -i hosts.yaml -m ping all
lima-default | SUCCESS => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python3"
    },
    "changed": false,
    "ping": "pong"
}

---

It is similar to the deprecation of the lima show-ssh default command, that is replaced with ssh lima-default

We should make a better job of documenting how to use the lima instances, with ansible playbooks (or with ssh).

Note: The commands above assumes that the lima instances have been added to the ssh config file (~/.ssh/config):

Include $HOME/.lima/*/ssh.config

[squeeb]

Ahaa, this has worked great. Thanks.

Another option for those of us not modifying ~/.ssh/config is to use the ansible inventory parameter:

ansible_ssh_common_args: -F "{{ lookup('env', 'HOME') }}/.lima/*/ssh.config"

[afbjorklund]

Right, but then it won't work for ssh and sftp and rsync and whatnot. But for ansible commands, sure.