go-pg doesn't follow any fixed constraint name conventions.

type TestAccess struct {
	Id        string   `pg:"type:uuid,default:uuid_generate_v4()" json:"id"`
	BatchId   string   `pg:"type:uuid,on_delete:CASCADE,unique:batch_id_test_id" json:"batch_id,omitempty"`
	Batch     *Batch   `json:"batch,omitempty"`
	StudentId string   `pg:"type:uuid,on_delete:CASCADE" json:"student_id,omitempt

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

Hello

I would like to have pgbouncer-exporter as a sidecar for the connection pooler.
I don't think it's possible right now.

It would be great to have the same options for sidecars as in the cluster.

What would you like to be added:

Currently config uses one file per environment (eg. dev, staging, prod, etc) we should move to a multi-file config where we have one folder per environment and config values can be split across multiple files within this folder.

Why is this needed:

For setups where there are