darron/sifter

Issues

• Does this work with other kinds of watches?

  #5 opened 4 years ago by darron
  7

• pass the original stdin to the program called by sifter

  #12 opened 8 years ago by alisade
  7

• consul watch key behavious same as event watch in terms of duplicate firing?

  #13 opened 8 years ago by mg03
  1

• Can we use less consistency for the checks?

  #9 opened 9 years ago by darron
  1

• Is it possible to use an IP or hostname other than localhost?

  #11 opened 8 years ago by ssenaria
  6

• No "output" in logs when watch fires?

  #10 opened 8 years ago by ssenaria
  10

• Capture the exit status of the program we're running.

  #8 opened 9 years ago by darron
  0

• We're completely ignoring any Consul Event Payload.

  #4 opened 9 years ago by darron
  0

• Switch from cobra cli to Viper.

  #7 opened 9 years ago by darron
  1

• Timeout when there's nothing on STDIN.

  #6 opened 9 years ago by darron
  0

• It's less than useful that you never get any feedback from a Consul `event`.

  #3 opened 9 years ago by darron
  1

• Once you send your first event.

  #2 opened 9 years ago by darron
  3

• `sudo` may not work because of the way I did `runCommand`.

  #1 opened 9 years ago by darron
  1