Custom Rules and Version Lock Integration

[vince-kelly]

I have gone thru and followed the documentation necessary for implementing custom rules. I realized the solution provided to implement custom rules also utilizes "bypass_version_lock=True", in turn rendering their automated versioning system unusable. I went ahead and tried setting this configuration to false for testing and was met with various validation errors flagged on my custom rule when using --update-version-lock in the dev function.

I was wondering if there's a pre-existing solution to not only implement custom rules but also utilizes the automated versioning system provided by the tool with my custom rules. Thanks.

[eric-forte-elastic]

👋 Hi @vince-kelly, thanks for the feedback. To me this looks like a configuration issue, could you expand on why you might need to bypass the version lock and what is not working for you?

Using the version lock file with custom rules is supported, and bypass_version_lock is an optional parameter. The limitation is that the version lock file version will be used as opposed to the Kibana version. We expect many of our users to manage rules via Kibana's UI so we recommend for those who do this to bypass the version lock to allow for authoritative versions from Kibana.

In one of our demo videos, you can see how we have also shown DaC command usage with the version lock file. E.g. this auto-generated PR 9 from our original demo video (link at proper timestamp).