I'm thinking instead of trying to build out integrations directly as part of this project, we just leave it open ended and allow the success handler to run an action set in the hypd configuration file. Perhaps some common integrations could be in separate repositories.
functionsuccessHandler(srcIPstring){// TBD: Implement loading successActionArgs from config// Replace token '<srcip>' with the value of srcIPfori,arg:=rangesuccessActionArgs{ifarg=="<srcip>"{successActionArgs[i]=srcIP}}os.Exec(successActionArgs...)}
I'm thinking instead of trying to build out integrations directly as part of this project, we just leave it open ended and allow the success handler to run an action set in the hypd configuration file. Perhaps some common integrations could be in separate repositories.
```golang
function successHandler(srcIP string) {
// TBD: Implement loading successActionArgs from config
// Replace token '<srcip>' with the value of srcIP
for i, arg := range successActionArgs {
if arg == "<srcip>" {
successActionArgs[i] = srcIP
}
}
os.Exec(successActionArgs...)
}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I'm thinking instead of trying to build out integrations directly as part of this project, we just leave it open ended and allow the success handler to run an action set in the hypd configuration file. Perhaps some common integrations could be in separate repositories.
Added in
79aa8136c5