You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand I and the NTP Project may be the last users of BK. That's OK.
I'd like a way to get a list of all possible trigger names.
I've been using BK long enough that I have seen the list of trigger names change, and I have a trigger handling mechanism where it is Good if I can automatically check the list of trigger names in case a new release (I'm not holding my breath) happens to change the list of trigger names.
The text was updated successfully, but these errors were encountered:
The big if block gives you all the possible values for cmd and if you grep for where trigger() is called you will set all the possible values you when.
But looking at the code I see what you probably want. Set BK_SHOW_TRIGGERS=/tmp/bk-triglist.txt in the environment and it will write a debug file with all the trigger for a given command.
Thanks, Wayne, and in this case I'm looking for something I can run as opposed to something a human has to look at. I know I can pipe the output of 'bk help trigger' and search for pre- and post-, but that finds extra keywords that are not correct, and it's also possible that the 'man' process will hyphenate things to make a line shorter. If I could, for example, just say 'bk trigger list' (or similar) and get the actual known list, that would be ideal. I note this here just to have it as an 'issue', as it's something we will likely choose to fix at some point.
I understand I and the NTP Project may be the last users of BK. That's OK.
I'd like a way to get a list of all possible trigger names.
I've been using BK long enough that I have seen the list of trigger names change, and I have a trigger handling mechanism where it is Good if I can automatically check the list of trigger names in case a new release (I'm not holding my breath) happens to change the list of trigger names.
The text was updated successfully, but these errors were encountered: