-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: use ansible_facts instead of ansible_* variables #474
fix: use ansible_facts instead of ansible_* variables #474
Conversation
5056013
to
9691f17
Compare
Docs Build 📝Thank you for contribution!✨ This PR has been merged and the docs are now incorporated into |
ba5a95c
to
70f4b04
Compare
70f4b04
to
904c929
Compare
904c929
to
dd96c89
Compare
f82c52c
to
e5b1f6a
Compare
I have no idea about the failing fail2ban roles. This seems to be broken in every pull request. Can somebody give me a hint, how to fix that? Or can this be fixed on the |
seems like 308 error are not handled in fail2ban check prior to version 3.11.0 python version |
If that is only fixed in Python 3.11, tests for Ansible <2.14 can not be fixed as they do not support that new Python version. |
the 308 redirect is kinda new, since it seems only to be done for fail2ban 0.10.2 released on November 20th. downloading the release 0.10.1 checksums only goes through a 301. |
I added a post in gitlab's forum, after some investigation the issue seems to be a double "/" in a 302 that leads to a 308 on the gitlab side. |
here is the link to the gitlab issue : https://gitlab.com/gitlab-org/gitlab/-/issues/508161 |
to allow ANSIBLE_INJECT_FACT_VARS to become false Signed-off-by: Marcus Klein <[email protected]>
e5b1f6a
to
066188f
Compare
Rebased to include #507. Now everything's green. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks
to allow ANSIBLE_INJECT_FACT_VARS to become false.
fixes #297