Hi,
Is it possible (since 2.0.0 or otherwise) to enforce constraints on the author/committer email when using Dolt via the CLI in combination with the remotes API?
Context
I would like to ensure that commit emails:
- follow a valid format
- optionally match a specific domain
Right now, users can set arbitrary emails locally in their config.
Dolt Workbench enforces this via HTTP headers (e.g., through nginx or another reverse proxy). As I understand from #10104, the same is true for SQL-based authenticated users since 2.0.0.
Something similar for CLI/remotes would be very helpful—for example, enforcing or deriving identity from authenticated headers instead of relying on the user (potentially misconfigured) Dolt config.
Questions
Is there a way to enforce email or username constraints today?
Are there recommended workarounds?
Hi,
Is it possible (since 2.0.0 or otherwise) to enforce constraints on the author/committer email when using Dolt via the CLI in combination with the remotes API?
Context
I would like to ensure that commit emails:
Right now, users can set arbitrary emails locally in their config.
Dolt Workbench enforces this via HTTP headers (e.g., through nginx or another reverse proxy). As I understand from #10104, the same is true for SQL-based authenticated users since 2.0.0.
Something similar for CLI/remotes would be very helpful—for example, enforcing or deriving identity from authenticated headers instead of relying on the user (potentially misconfigured) Dolt config.
Questions
Is there a way to enforce email or username constraints today?
Are there recommended workarounds?