Uploaded image for project: 'Trapperkeeper'
  1. Trapperkeeper
  2. TK-86

validate service config before startup

    Details

    • Type: New Feature
    • Status: Ready for Engineering
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:

      Description

      Most TK services have some required config, and, when any one of these config values are missing, will fail to init or start. Currently, it is up to each service to validate it's config data, and the only way for services to handle this is to throw an Exception - this is undesirable because the stacktrace is almost always useless, and is very distracting to an end-user looking at the log and trying to diagnose this problem.

      I propose that we add some sort of way for TK services to define their required configuration. TK would then verify that each service's required configuration is available before init; if any configuration is missing, the process should terminate with a user-friendly error message which mentions all of the missing config values (not just the first one encountered).

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  kevin.corcoran Kevin Corcoran
                  QA Contact:
                  Ryan Gard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: