Broker audit -- ensure broker modules have proper form validation, testing, and documentation.

[jchate6]

Broker audit -- ensure broker modules have proper form validation, dependencies, testing, and documentation.

• Install and configure each Broker on TOM Demo
• • ALeRCE --> tom_alerts
• • ANTARES --> tom_alerts
• • Lasair --> tom_alerts
• • Hermes --> tom_hermes
• • Scout --> tom_alerts (Not Including)
• • TNS --> tom_alerts
• • Fink --> tom_fink
• • Gaia --> tom_alerts
• Check and update documentation
• • ALeRCE
• • ANTARES
• • Lasair
• • Hermes
• • Scout
• • TNS
• • Fink
• • Gaia
• Test each broker to make sure it behaves as expected
• • ALeRCE
• • ANTARES
• • Lasair
• • Hermes
• • Scout
• • TNS
• • Fink
• • Gaia
• Update Canary tests
• • ALeRCE
• • ANTARES
• • Lasair
• • Hermes
• • Scout
• • TNS
• • Fink
• • Gaia
• address and/or prioritize broker issues
• Investigate Pitt-Google Broker
• Develop regular maintenance strategy
• Review tom_alerts_dash

[jchate6]

I'm failing to find any basic information about setting up a Broker (TNS, ALeRCE, Lasair, etc.) in the documentation.
This should be made more explicit.

For example,
TNS requires the following in settings.py:

BROKERS = {
    'TNS': {
        'api_key': TNS_API_KEY,
        'bot_id': <<bot_id>>,
        'bot_name': <<bot_name>>,
    }
}

[jchate6]

Related to TOMToolkit/tom_fink#24

[jchate6]

Look into more modern ways to access the Gaia Broker Data.