-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change request: make ara fail-safe for playbooks #124
Comments
+1 |
Hi, thanks for the feedback. I feel like this would be a shared responsability between Ansible itself and ARA. As far as I am aware, this is currently the case -- throughout the development of ARA, there has been multiple times where ARA was erroring out with a stack trace and it didn't prevent Ansible from running. In case of timeouts, or latency related issues, it's a bit more nuanced. In the context of ARA, we're not enforcing any kind of timeouts right now so I guess we are essentially using defaults provided by sqlalchemy, whatever they are. Putting timeouts too low is something we have to be wary of, but we could surely do a better job at exception handling. |
I've created an issue for this upstream: ansible/ansible#27705 |
Hi there.
Here are my thoughts. There should be config option to let ara fail silently - if it fails to do or log something, it should not break the playbook it is used in. Option would be usable in production-critical playbooks - ara problems(like insufficient disk space at ara db) should not stop my playbooks main functionality - configure production systems.
The text was updated successfully, but these errors were encountered: