ansible/roles/docker-distribution
Michal Konecny 2ec055db6f Use first uppercase letter for all handlers
This will unify all the handlers to use first uppercase letter for
ansible-lint to stop complaining.

I went through all `notify:` occurrences and fixed them by running
```
set TEXT "text_to_replace"; set REPLACEMENT "replacement_text"; git grep
-rlz "$TEXT" . | xargs -0 sed -i "s/$TEXT/$REPLACEMENT/g"
```

Then I went through all the changes and removed the ones that wasn't
expected to be changed.

Fixes https://pagure.io/fedora-infrastructure/issue/12391

Signed-off-by: Michal Konecny <mkonecny@redhat.com>
2025-02-10 20:31:49 +00:00
..
defaults Fix majority of remaining yamllint warnings and errors 2024-11-28 17:31:45 +10:00
files Fix logrotate for docker-distribution 2021-02-04 06:48:28 -05:00
handlers Fix name[casing] ansible-lint issues 2025-01-14 20:20:07 +10:00
meta Fix meta-incorrect linting issues 2025-01-21 15:40:59 +10:00
tasks Use first uppercase letter for all handlers 2025-02-10 20:31:49 +00:00
templates Allow delete on candidate registery so we can clean up old images. 2018-09-24 22:00:57 +00:00
vars add osbs w/ v2 registry support 2016-01-28 20:31:13 +00:00
README.md add osbs w/ v2 registry support 2016-01-28 20:31:13 +00:00

Role Name

A brief description of the role goes here.

Requirements

Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.

Role Variables

A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.

Dependencies

A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.

Example Playbook

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

- hosts: servers
  roles:
     - { role: username.rolename, x: 42 }

License

BSD

Author Information

An optional section for the role authors to include contact information, or a website (HTML is not allowed).