project-config/playbooks/translation
Clark Boylan 2db422f0b8 Run ansible-lint on Ubuntu Noble
We ran into issues getting ansible-lint to run on Noble without updating
everything to current ish versions due to Python 3.12 compatibility
issues. Updating everything in this way created a bunch of new lint
errors we need to fix so we worked around the problem previously by
pinning back to Jammy.

Now we move the job back to Noble (the default Nodeset) and update the
tooling and fix the linter errors. This should allow us to move forward
in a productive manner on modern platforms.

The linter errors we fix include:

 * Naming every play
 * Ensuring every play name starts with a capital letter
 * Using fully qualified collection names for action modules
   (archive, git_config, and synchronize)
 * Quoting octal file modes

Change-Id: I96560c5ce2a5af39d39b3fc339862932a856bd13
2024-08-21 12:55:46 -07:00
..
openstack-translation-artifacts.yaml Run ansible-lint on Ubuntu Noble 2024-08-21 12:55:46 -07:00
post.yaml Run ansible-lint on Ubuntu Noble 2024-08-21 12:55:46 -07:00
pre.yaml Run ansible-lint on Ubuntu Noble 2024-08-21 12:55:46 -07:00
propose-translation-update.yaml Run ansible-lint on Ubuntu Noble 2024-08-21 12:55:46 -07:00
upstream-translation-update.yaml Run ansible-lint on Ubuntu Noble 2024-08-21 12:55:46 -07:00