Support YAML anchors in sqlc.yaml

[kevinvalk]

What do you want to change?

Currently I am working on a microservices project using SQLC. All is fine, but I find myself repeating the same configuration options for each codegen section. Using YAML anchors this would be trivial and very nice, but this is currently not supported.

Then I could do something like the following.

sql:
 - schema: database
 queries: services/a
 engine: postgresql
 codegen:
 - out: gateway/src/gateway/services/organization
 plugin: py
 options: &base-options
 query_parameter_limit: 1
 package: gateway
 output_models_file_name: null
 emit_module: true
 emit_generators: false
 emit_async: true

 - schema: database
 queries: services/b
 engine: postgresql
 codegen:
 - out: gateway/src/gateway/services/project
 plugin: py
 options: *base-options

https://play.sqlc.dev/p/32c6b52785ce13ddfeb2311a2a835800d2578b56bf1addd95887e3fe45d2ace0

What database engines need to be changed?

No response

What programming language backends need to be changed?

No response

[kyleconroy]

We parse YAML using https://github.com/go-yaml/yaml which has support for anchors. You can see a working example here.

version: "2"
sql:
- schema: "query.sql"
 queries: "query.sql"
 engine: "postgresql"
 gen:
 go: 
 package: "authors"
 out: "postgresql"
 database:
 uri: "postgresql://postgres:postgres@localhost:5432/postgres"
 rules: &base-rules
 - sqlc/db-prepare
- schema: "query.sql"
 queries: "query.sql"
 engine: "postgresql"
 gen:
 go:
 package: "authors"
 out: "mysql"
 rules: *base-rules

The bug you're seeing is due to how the plugin system serializes options. I've updated this issue to be a bug report.