playbook
Here are 539 public repositories matching this topic...
-
Updated
Jun 9, 2020 - Swift
We'd like to support CentOS8!
Ideally we'd have testing for:
- kitchen with vagrant (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.kitchen.vagrant.yml)
- kitchen with docker (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.kitchen.yml)
- travis (https://github.com/dev-sec/ansible-ssh-hardening/blob/master/.travis.yml)
Docker-Image that should be used: https
Looks like there is no reference of mariadb_server__delegate_to in any task file of the role.
more cli commands
After a discussion about reasonable use of comments, we thought it worth providing a couple of extra examples of where comments in code are useful (to complement the general rule that code should be self-documenting).
For example, from @morgaan "comment for tricks dictated by business needs"
When we start using xibs we will have to name the IBAction methods and the corresponding delegate methods to the ViewController
@IBAction func didPressLogin(_ sender: Any)
In the spirit of this article: http://khanlou.com/2016/09/swifty-delegates/ we agreed on naming the delegates like this:
func didPressLogin(on authView: UIView)
I am aware there have been a number of Community version related issues eg #85 and #219 but I was wondering how you would feel about a PR adding some more documentation and maybe configuration to this stack.
As a user I would love to have it documented specifically that I can utilize community-only things by setting certain parameters. Also exclude certain packages from the install stack.
And
-
Updated
May 16, 2020 - YAML
In
https://github.com/freeipa/ansible-freeipa/blob/master/README-topology.md
It would be really helpful to see what the ansible for creating a tight-cell topology of ipa servers looks like. Please and thanks!
We'd like to support CentOS8!
Ideally we'd have testing for:
- kitchen with vagrant (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.kitchen.vagrant.yml)
- kitchen with docker (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.kitchen.yml)
- travis (https://github.com/dev-sec/ansible-nginx-hardening/blob/master/.travis.yml)
Docker-Image that should be used:
According to the documentation for http_publish_uri the wildcard address 0.0.0.0 is only permissable if set via $http_bind_address. Which is the default if http_publish_uri remains unset. For default in the role http_publish_uri is set to "http://0.0.0.0:9000" which is an invalid value. The graylog-server defaults to the, probably first, non-loopback ipv4 address, however it logs this fact every s
-
Updated
Jun 28, 2020 - Python
Allow a developer to build/test/iterate on APB development to a remote cluster without requiring docker usage on their local machine.
This issue was raised by @akostadinov
-
Updated
May 21, 2019
We'd like to support CentOS8!
Ideally we'd have testing for:
- kitchen with vagrant (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.kitchen.vagrant.yml)
- kitchen with docker (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.kitchen.yml)
- travis (https://github.com/dev-sec/ansible-mysql-hardening/blob/master/.travis.yml)
Docker-Image that should be used:
Currently iptables is completely disabled for RHEL 6 because I don't like dealing with iptables. If someone could fix that, it would be just great.
I've been attempting to deploy OKD to BYO Infrastructure by setting
openshift_deployment_type: origin
deployment_type: origin
Currently running into the error:
Error reading manifest latest in registry.redhat.io/openshift/origin: unknown: Not Found
I'm assuming there's issues with my configuration but can't seem to find documentation on how to use casl-ansible for an OKD depl
Add Example Usage
what
- Add example invocation
why
- We need this so we can soon enable automated continuous integration testing of module
-
Updated
Feb 23, 2020 - Shell
Improve this page
Add a description, image, and links to the playbook topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the playbook topic, visit your repo's landing page and select "manage topics."
Describe the bug
Modifying
/etc/pam.d/system-auth-acas seen here is wrong as it "breaks" theauthconfigway. Apparently a symptom was also witnessed in #23.Normally the file begins with: