Add tests for Loggly integration

[ethho]

Discussed during Ethan <> Shweta meeting 7/28/2021.

• [x] Debug posting to Loggly on Shweta's local env
  • Assignee: @shwetagopaul92
• [x] Pytest (passing in tox) that checks status_code == 200 returned by POST to Loggly
  • Assignee: @eho-tacc
• [x] Pytest (passing in tox) that assert Reactor().settings.loggly.customer_token is not None
  • Assignee: @eho-tacc
• [x] We need to cover the use case where a base image with Loggly integration receives a 200 response from Loggly.
  • Assignee: @eho-tacc
  • Solution: Run pytests again, but within base image
  • Currently, GH CI does not run pytests in the base image: https://github.com/TACC-Cloud/python-reactors/blob/619c391e18667f6b8e5240cc1d9ad3b47aaaa31e/.github/workflows/docker-publish.yml#L94-L94

[ethho]

@shwetagopaul92 any updates on Loggly manual local testing?

[shwetagopaul92]

@eho-tacc Yes, the manual testing worked fine. I have attached a screenshot to show the logs on Loggly Interface. I am currently working from the branch feat-loggly-integration to add tests with the customer_token set in Github Secrets.

[ethho]

On feat-loggly-integration 8a5cc54:

$ tox -- -k 'loggly'
# ...
FAILED tests/test_logs.py::test_loggly_log[R_tp_opt] - NameError: name 'self' is not defined
FAILED tests/test_logs.py::test_loggly_log[R_bare] - NameError: name 'self' is not defined
======================================== 2 failed, 2 passed, 46 deselected, 4 warnings in 0.83s ========================================

[ethho]

Coverage in the following pytest: https://github.com/TACC-Cloud/python-reactors/blob/135191ba4c4195d76ab0d170da3923f51a786109/tests/test_logs.py#L132-L158