SUMMARY
The requirement for vault credentials should be removed.. or perhaps a new module without them could be created. Using the ansible-vault is no longer the only/best way to encrypt and protect credentials. I, like others I suspect, use the full Ansible Automation Platform with which store credentials natively, allowing you to associate with the template or inject as something like an env variable. And because there are no other collections or modules for Logicmonitor, there are no alternatives except direct API calls.
ISSUE TYPE
In my current situation, I am developing rulebooks to handle ACKing and SDTing alerts. The current process involves storing a Bearer token in AAP then injecting as an env var. Being required to use a vault is normal for ansible-core but a step backwards for AWX, Tower or AAP.
COMPONENT NAME
webhook.py
ADDITIONAL INFORMATION
SUMMARY
The requirement for vault credentials should be removed.. or perhaps a new module without them could be created. Using the ansible-vault is no longer the only/best way to encrypt and protect credentials. I, like others I suspect, use the full Ansible Automation Platform with which store credentials natively, allowing you to associate with the template or inject as something like an env variable. And because there are no other collections or modules for Logicmonitor, there are no alternatives except direct API calls.
ISSUE TYPE
In my current situation, I am developing rulebooks to handle ACKing and SDTing alerts. The current process involves storing a Bearer token in AAP then injecting as an env var. Being required to use a vault is normal for ansible-core but a step backwards for AWX, Tower or AAP.
COMPONENT NAME
webhook.py
ADDITIONAL INFORMATION