Enforce strict syntax for replication zone configurations #124520
Labels
A-cli-client
CLI commands that pertain to using SQL features
A-cluster-observability
Related to cluster observability
A-sql-cli-observability
Issues related to surfacing SQL observability in SHOW, CRDB_INTERNAL, SYSTEM, etc.
A-sql-observability
Related to observability of the SQL layer
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-observability
Is your feature request related to a problem? Please describe.
Customer made a typo and parser/cli did not notify the customer, causing them to believe the replication zone was correctly configured while in reality it was not.
Describe the solution you'd like
Customer would like to have strict enforcement of semantics and syntax for replication zone configurations. Customer would also like the parser to error out if the syntax is incorrect for replication zone configurations.
Describe alternatives you've considered
Not applicable
Additional context
Full scenario showing the differences when customer made a typo / used wrong syntax:
The following caused the incorrect
lease_preference
although no error was thrown:and this is the correct syntax:
Full examples below
Bad Syntax
Good Syntax
Jira issue: CRDB-38941
The text was updated successfully, but these errors were encountered: