allow /usr/local/pkg as an include dir for function calls

[ndejong]

allow /usr/local/pkg as an include dir for function calls

[ndejong]

I've taken a look at this and got "something" that probably works at the sacrifice of some stability which itself can be addressed with further effort.

I've taken moment to pause though as I'm not sure I'm comfortable with opening up the universe of possible includes like this - part of the reason the function_call is so rigid about what can be included is that I did not want to enable functionality that led to unexpected outcomes ... and it is already in uncharted territory in that regard..

If anyone can describe more reasons why this is an important must-have extension of capability then I'll make it happen.

Will keep this ticket open for the time being.

[travisghansen]

@ndejong I'm just using the built-in xmlrpc API now which supports this idea along with anything else so I'm good for now.

[ndejong]

That's interesting - could you describe this a little bit more - would it perhaps make sense for FauxAPI to have an xmlrpc endpoint perhaps?

Reference
https://github.com/users/ndejong/projects/2#card-18935721

[travisghansen]

Basically pfSense has an xmlrpc API that somewhat eliminates the need to use this project. In my use case, I was developing a piece of software to integrate with pfSense and wanted to make the 'barrier to entry' as low as possible. Requiring users to install/setup the fauxapi in conjunction with the limitation(s) originally mentioned on this ticket were factors in directly using the built-in xmlrpc api (I was unaware of the extent of features it offered...which is basically anything you need/want and more).

None of this is meant to demean this project FYI. Just stuff I discovered along the way.

• https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/xmlrpc.php
• https://github.com/travisghansen/kubernetes-pfsense-controller

[ndejong]

Ahh - that's awesome, certainly do like your kubernetes-pfsense-controller too - dare I say it, did you consider using OPNsense rather than pfSense for this though? I've been doing a lot more with OPNsense of late (https://github.com/verbnetworks) and find the OPNsense code much cleaner etc.

[travisghansen]

@ndejong I've used pfsense for a long time and didn't follow the IMO petty banter between the 2 projects (from both sides from what I can tell).

Perhaps in the future I'll take a look but I've been running the installations I have in production for many years and didn't want to mess with those installs.

Having said that, I have nothing against the newer project and my controller could pretty easily be adapted to opnsense if the API supports all needed functions.

I have plans to tie into fail2ban (with kubernetes logs) but instead of making iptables call it would make rules in pfsense. Kinda lofty goal but doable :)

[nasirhafeez]

Hi,

A possible use case that I've encountered for this: I'm trying to automate some SquidGuard functions, and SquidGuard requires the Apply button in General Settings to be pressed after making changes.

This runs the sg_reconfigure() function from /usr/local/pkg/squidguard.inc in the background. If FauxAPI were to support included files from /usr/local/pkg directory then one could use function_call to execute sg_reconfigure() via FauxAPI.

Other than that, I don't see how one could do this via FauxAPI.