rule-engine

It would be useful if Kuiper supported file-based rule and stream provisioning (i.e. importing) on startup. Currently rules and streams need to be created by someone using the client, or an application requesting creation via the Kuiper REST API.

Supporting file-based provisioning would allow someone to deploy Kuiper with a pre-defined set of streams and rules, removing the need for someone (or

Hello, I read the example:

...

type User struct {
Name string
Age int64
Male bool
}

func (u *User)GetNum(i int64) int64 {
return i
}

func (u *User)Print(s string){
fmt.Println(s)
}

func (u *User)Say(){
fmt.Println("hello world")
}

const (
base_rule = ...
func exe(user *User){
dataContext := context.NewDataContext()
//inject struct
dataContext.Add

Currently PSRule supports Windows using PowerShell 5.1 and above.

This is great for Windows administrators however not great for everyone else. When enabling validation within a CI/CD pipeline, the agent platform might not be Windows.

Containers provide portability and consistency which is very applicable for PSRule.

PowerShell is already available in a published [Docker container](https: