```
[DEPRECATION WARNING]: community.general.yaml has been deprecated. The plugin
has been superseded by the the option `result_format=yaml` in callback plugin
ansible.builtin.default from ansible-core 2.13 onwards. This feature will be
removed from community.general in version 13.0.0. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg
```
Mitigates ansible-lint warnings of type 'schema':
% ansible-lint -t schema
WARNING Listing 4 violation(s) that are fatal
schema[playbook]: None is not of type 'array'
host-beaker.yml:1 Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.
This rule is not skippable and stops further processing of the file.
If incorrect schema was picked, you might want to either:
* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.
schema[playbook]: None is not of type 'array'
host-hobbes.yml:1 Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.
This rule is not skippable and stops further processing of the file.
If incorrect schema was picked, you might want to either:
* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.
schema[playbook]: None is not of type 'array'
host-oganesson.yml:1 Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.
This rule is not skippable and stops further processing of the file.
If incorrect schema was picked, you might want to either:
* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.
schema[playbook]: None is not of type 'array'
host-unicorn.yml:1 Returned errors will not include exact line numbers, but they will mention
the schema name being used as a tag, like ``schema[playbook]``,
``schema[tasks]``.
This rule is not skippable and stops further processing of the file.
If incorrect schema was picked, you might want to either:
* move the file to standard location, so its file is detected correctly.
* use ``kinds:`` option in linter config to help it pick correct file type.
Read documentation for instructions on how to ignore specific rule violations.
Rule Violation Summary
count tag profile rule associated tags
4 schema[playbook] basic core
Failed after min profile: 4 failure(s), 0 warning(s) on 137 files.
Link: Netz39_Admin/netz39-infra-ansible#516
The previous variable name is the same as in the role
24367dfa.dehydrated but had a different meaning here. While in the
dehydrated role it means the directory where the working copy of the
dehydrated git repo is cloned to, in here it meant the directory for the
challenges which is known as "wellknown" dir in the dehydrated project
and role. Setting this variable before using both roles would most
certainly lead to unexpected results?!
The whole playbook does not set `dehydrated_location` so it goes with
its defaults in both roles currently, probably.
Consistent with the role setup_http_site_proxy now, which configures the
path in the reverse proxy, while this configures the same path in the
actual webserver behind the proxy.
Running the playbooks using both roles yields no change in target
configuration after this changeset.
Link: https://github.com/24367dfa/ansible-role-dehydrated/blob/main/defaults/main.yml
Fixes: 1fe6526898 ("✨ Add a role to allow letsencrypt access in Apache2")
