Matt Uebel

master to manager terminology change breaks the playbooks

3

**Describe the bug** The base configs from splunk have changed the terminology from `master` to `manager`. This breaks the playbooks. **Additional context** This happened once I got to the cluster...

pip3 ansible package needed when running on ubuntu 20.04

1

Opening this one for visibility, and perhaps an update to the docs Received this error running deploy_site.yml: ``` Malformed output discovered from systemd list-unit-files ``` Saw similar message at https://github.com/DataDog/ansible-datadog/issues/274...

lxml module needed for license manager role

1

**Describe the bug** Playbook failed at the license manager role. ``` ModuleNotFoundError: No module named 'lxml' ``` **Desktop (please complete the following information):** ubuntu 20.04.1 ansible 2.14.4 python 3.8.10 **Additional...

and a description as well!

currently this only runs in the context of one runner this only works for an environment with one of each config management system making this work for arbitrary number of...

it's not clear that someone could just fork these repos and use the code for their own purposes consider iterating on the repos to make this possible. An alternative approach...

currently workflow has SHC member hardcoded this should be templated https://github.com/MattUebel/git-good-splunk-shcdeployer/blob/main/.github/workflows/deploy.yml

either eliminate the warnings or make sure they only flag config that is part of the changes made in the PR

mostly applicable to https://github.com/MattUebel/git-good-splunk-indexmanager , but it would be nice to know if your PR is going to cause a rolling restart of the infrastructure once it's merged and deployed...