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

Allow shutting down with non-zero exit status, but no backtrace

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Froyo
    • QA Risk Assessment:
      Needs Assessment

      Description

      This is useful when a program has already reported a friendly error message on say stderr and/or to the log. The issue arose when puppetdb wanted to initiate a shutdown after detecting that the currently available database was unsupported.

      I could imagine allowing an exit status argument to (shutdown ...), though I suppose we'd have to define how competing requests are handled.

      Another option might be support for throwing something like

      (ex-info ... {:kind ::tk/notify-and-exit :status 2 :message "something for *err*, etc."})
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            rob.browning Rob Browning
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Zendesk Support