Anyone with Ansible/AWX experience accessing HTTP APIs on protected networks?

I have tried documentation, the global web and chat with colleagues. Time to bring on the fedi human search.

Using ansible on switches that require you to come from a protected network is easy, you set up your ssh command to go through a jumphost. Accessing switches or firewalls that use an HTTP API is easy, you use a package that talks to the HTTP API, probably using the httpapi package.

But an HTTP API where you need to come from a protected network? Manually it's easy, just `ssh -D` to a jumphost/bastion in the right network and tell curl to use a SOCKS proxy.

On the Ansible side though, I can't find the right place to get httpapi to go through a SOCKS proxy, and I'm not sure where's the best place to run that ssh command.

Has anyone on Fedi already solved this problem?

#Ansible #AnsibleTower #AWX

Looking for #AnsibleTower alternatives? You might want to give #AnsibleSemaphore a try. This #HowTo provides the basic installation instructions as well as a ready to use #Box for #Vagrant.

https://gyptazy.ch/blog/howto-install-ansible-semaphore-ui-on-debian-12/

#Ansible #Tower #AAP #AAP2 #Automation #AutomationPlatform #devops #redhat #debian #linux #cicd #dev
Howto install Ansible SemaphoreUI on Debian 12

Howto install Ansible SemaphoreUI on Debian 12

OSiUX Ansible

OSiUX Ansible Posts and Videos

OSiUX

Cómo corregir error "tower_(cli).exceptions.TowerCLIError: failed to parse some of the extra variables"

#Ansible #AnsibleTower #automation #AWX #cfg #cli #config #DevOps #error

https://osiux.com/2019-04-10-awx-ansible-tower-cli-failed-to-parse-some-of-the-extra-variables.html

AWX Ansible =tower_cli.exceptions.TowerCLIError: failed to parse some of the extra variables=

Cómo corregir error

OSiUX

Cómo corregir error "tower_(cli).exceptions.TowerCLIError: failed to parse some of the extra variables"

#Ansible #AnsibleTower #automation #AWX #cfg #cli #config #DevOps #error

https://osiux.com/2019-04-10-awx-ansible-tower-cli-failed-to-parse-some-of-the-extra-variables.html

AWX Ansible =tower_cli.exceptions.TowerCLIError: failed to parse some of the extra variables=

Cómo corregir error

OSiUX

Utilidades y Deploy desantedido de recursos de AWX utilizando Ansible
Tools

#Ansible #AnsibleTower #AWX #BASH #Git #JSON #YAML

https://osiux.com/2022-10-03-ansible-tools-v0-3-0.html

/Ansible Tools/ =v0.3.0=

OSiUX
Red Hat trennt sich vom monolithisch konstruierten Ansible Tower und nennt den Nachfolger Automation Platform 2. Der besteht aus unabhängigen Komponenten.
Automatisierungstool: Ansible Tower wird durch Automation Platform 2 ersetzt
Automatisierungstool: Ansible Tower wird durch Automation Platform 2 ersetzt

Red Hat trennt sich vom monolithisch konstruierten Ansible Tower und nennt den Nachfolger Automation Platform 2. Der besteht aus unabhängigen Komponenten.

Is there a trivial way to determine which #AnsibleTower release corresponds to roughly which #AWX release?

Ansible Tower has release notes and clear requirements etc, Red Hat is starving AWX of this kind of information to create the incentive to buy the product.

The official answer is of course "just get your company to buy Ansible Tower", but that's not the environment I'm in and not the answer I'm looking for.
LIBRANET.de | Search

Question #ANSIBLETOWER du jour,
Comment forcer un playbook winrm à sortir sur une patte réseau (via http) du srv ansible alors que ça gaze en commande ad-hoc sur ce même serveur? #devops
以下のタグの Qiita 記事がこの1時間に投稿されました。
➖➖➖➖➖➖➖➖➖➖
#actionsongoogle
#android
#ansible
#ansibletower
#bitcoin
#blockchain
#buildroot
#chrome
#gem
#go
#golang
#googlehome
#goutte
#homebrew
#java
#laravel
#laravel5
#linux
#mac
#phalcon
#php
#python
#python3
#rails
#raspberrypi
#smartspeaker
#仮想通貨
#未来電子
#組み込み
➖➖➖➖➖➖➖➖➖➖
各 Qiita 記事へのリンクは、このトゥートのスレッドに「非公開」もしくは「未収載」でトゥートされています。
スレッドを見るにはこのトゥートをクリックしてください。