This is essentially the same stop-gap zuul/zuul-jobs put in place
with I93b9634f7d2813cb1a17aeda2d8ef2ec188f86f3 for now, since it's
generating the same diagrams.
Change-Id: I682ffe9e89ed83b09405940d5cc9bdc66643e131
Older ansible-lint is broken due to an unpinned 'rich' dependency. Newer
ansible-lint fixes this issue. Update our test deps to address this.
Change-Id: I5dd4e4f66720800f140a9d15631adddb5d10cf6f
The ansible-lint utility is incompatible with Ansible 2.7 which is
now causing failures. Update to current Zuul versions.
Change-Id: If249ff4c51f9b89c6dbe0dccaad26f52727b36be
Ansible changed, then unchanged their behavior around file modes, but
being explicit is likely a good idea to handle any new future changes
from ansible.
We set modes generously (to 755 for dirs and 644 for files) to avoid
unexpected access problems. Note that depending on the perms in AFS this
may cause a perms ot update on existing dirs but that should be fine as
long as we aren't making them more restrictive.
Finally we skip two cases where modes are required by the linting rule
because they are tarball extraction steps and applying a single mode to
all dirs and files in a tarball doens't make a ton of sense.
Includes bumping linter configuration.
Change-Id: Iacf41549928ba7f05f0f71a79ddef1b6e1154e2a
Co-authored-by: Sorin Sbarnea <ssbarnea@redhat.com>
This is required in order to avoid this error:
ModuleNotFoundError: No module named 'setuptools'
The version of ansible-lint we were using has a bug which causes a
false positive on ensure-pip, so we update the ansible-lint version
to match that in zuul-jobs and update the skips accordingly. This
also flags lack of spaces in {{braces}} so those instances are
fixed.
Change-Id: I9d122631126ab65507f0a5616ff6741066a7acf8
Add usual linting job for this repo to have some basic testing.
Also, add the normal .gitignore to blacklist .tox and some other files.
Note this change is not self-testing since the repo is a config-project.
Change-Id: Ie54095f39f9bb4d10d6f809c573ea712f3885af6
Jeremy Stanley