fix typo disable_looups in inventory/proxmox

[tbjers]

SUMMARY

Resolve issue with lookups in proxmox inventory config.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

proxmox

ADDITIONAL INFORMATION

$ ansible-inventory -i my.proxmox.yml --graph
[WARNING]:  * Failed to parse /home/ansible/infrastructure/my.proxmox.yml with auto plugin: template() got an unexpected keyword argument 'disable_looups'
[WARNING]:  * Failed to parse /home/ansible/infrastructure/my.proxmox.yml with yaml plugin: Plugin configuration YAML file, not YAML inventory
[WARNING]:  * Failed to parse /home/ansible/infrastructure/my.proxmox.yml with ini plugin: Invalid host pattern '---' supplied, '---' is normally a sign this is a YAML file.
[WARNING]:  * Failed to parse /home/ansible/infrastructure/my.proxmox.yml with ansible_collections.community.general.plugins.inventory.proxmox plugin: template() got an unexpected keyword argument
'disable_looups'
[WARNING]: Unable to parse /home/ansible/infrastructure/my.proxmox.yml as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
@all:
  |--@ungrouped:

Once typo is fixed, it correctly lists hosts.

[felixfontein]

Thanks for your contribution! Can you please add a changelog fragment? Thanks!

[ansibullbot]

cc @Ajpantuso @Thulium-Drake @ilijamt @joshainglis @karmab @tleguern
click here for bot help

[github-actions]

Docs Build 📝

Thank you for contribution!✨

This PR has been merged and your docs changes will be incorporated when they are next published.

[patchback]

Backport to stable-5: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply fd436bd on top of patchback/backports/stable-5/fd436bdbc2917365580851a9a0cf940875633ea1/pr-5640

Backporting merged PR #5640 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-5/fd436bdbc2917365580851a9a0cf940875633ea1/pr-5640 upstream/stable-5

4. Now, cherry-pick PR fix typo disable_looups in inventory/proxmox #5640 contents into that branch:

   $ git cherry-pick -x fd436bdbc2917365580851a9a0cf940875633ea1

   If it'll yell at you with something like fatal: Commit fd436bdbc2917365580851a9a0cf940875633ea1 is a merge but no -m option was given., add -m 1 as follows intead:

   $ git cherry-pick -m1 -x fd436bdbc2917365580851a9a0cf940875633ea1

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR fix typo disable_looups in inventory/proxmox #5640 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-5/fd436bdbc2917365580851a9a0cf940875633ea1/pr-5640

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-6: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-6/fd436bdbc2917365580851a9a0cf940875633ea1/pr-5640

Backported as #5644

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@tbjers thanks for fixing this!

[tbjers]

@tbjers thanks for fixing this!

Thank you so much for merging so quickly!