Managing a unique DMZ

Get Help
, , ,
1

My team and I have encountered a unique issue when trying to find a solution for managing a unique DMZ -
We have a L7 gateway between us and the DMZ, that only supports http/ws
It also only accepts json/xml payloads (when coming into our network)

We’ve looked at receptors (doesn’t work for us from what we’ve seen)

We’ve also looked at ansible-pull that doesn’t use json/xml payloads even when cloning with https

Our leading idea is to implement our own “ansible-pull” mechanism that works with jsons

How would you guys tackle that?

2

I am not sure if I got the description right or what actually the problem could be in your case with something like

ansible-pull --inventory "$(hostname)," --url "https://git.example.com/repo.git"

But could be the following approach on/from the Remote Node an option for you?

ansible-playbook --inventory "$(hostname)," <(curl --silent https://raw.gitusercontent.example.com/repo/refs/heads/main/src/main.yml)

With this, one is able to run an Ansible playbook or other scripts out of a Remote Version Control System (VCS) like Git.

1 Like