080ecb4579
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>
11 lines
310 B
Plaintext
11 lines
310 B
Plaintext
---
|
|
parseable: true
|
|
exclude_paths:
|
|
- ../../zuul/zuul-jobs
|
|
- zuul.d
|
|
skip_list:
|
|
- '106' # Role name does not match ``^[a-z][a-z0-9_]+$`` pattern
|
|
- '204' # Lines should be no longer than 160 chars
|
|
- '301' # Commands should not change things if nothing needs doing
|
|
- '701' # No 'galaxy_info' found
|