[Bug]: Setting Branch Protection from lakectl fails

[itaiad200]

What happened?

What actually happened, including error codes if applies.

Steps to Reproduce:

1. Create a new repo.
2. use lakectl to create branch protection rule: lakectl branch-protect add lakefs://test main

You'll get a 400 bad response result. It works from the UI.
If a branch protection rules exist prior to the operation, then lakectl branch protection rule creation works.

Root Cause: lakectl first tries to fetch the rules and then uses Etag (checksum) for an atomic update. If no rule exists, then the value is an empty string which is forbidden. The Swagger API declares allowEmptyValue: true which is misleading. It allows for the header If-Match with no value, not an empty string value.

Expected behavior

The command should create a branch protection rule successfuly.

lakeFS version

latest

How lakeFS is installed

all

Affected clients

lakectl

Relevant log output

No response

Contact details

No response