fix(config): restore the go:generate directive so make generate works

[c1-squire-dev]

One line. pkg/config has no //go:generate directive, so the Makefile's

$(GENERATED_CONF): pkg/config/config.go go.mod
	@echo "Generating $(GENERATED_CONF)..."
	go generate ./pkg/config

is a silent no-op — it prints Generating pkg/config/conf.gen.go... and regenerates nothing. Running the generator directly instead (go run ./pkg/config/gen) does work, but the SDK's generator is os.Create("conf.gen.go"), relative to the working directory, so the file lands in the repo root and has to be moved by hand.

A //go:generate directive runs with the working directory set to the package, which fixes both halves at once.

This repo is the outlier: baton-datadog, baton-okta, baton-github and baton-slack all carry the same //go:generate go run ./gen line in pkg/config/config.go, against an otherwise byte-identical Makefile rule.

Verification

$ rm -f conf.gen.go && make generate
Generating pkg/config/conf.gen.go...
go generate ./pkg/config

$ git status --porcelain
 M pkg/config/config.go

conf.gen.go is regenerated in place, byte for byte identical to what was committed, and nothing is left in the repo root. The only change in the tree is this file's one added line.

Scope

config_schema.json and baton_capabilities.json are deliberately left alone. They are generated from the built binary rather than from config.go, so they move when the SDK moves — commit 85111b92 here rewrote 92 lines of baton_capabilities.json off a dependency bump with no config change at all. That is why generate-baton-metadata.yaml regenerates and commits them on merge to main, and why no connector's Makefile emits them. Adding them to a local target would produce files that go stale on the next SDK bump with nobody touching the repo.

[github-actions]

Connector PR Review: fix(config): restore the go:generate directive so make generate works

Blocking Issues: 0 | Suggestions: 0 | Threads Resolved: 0
Criteria: Criteria status: loaded .claude/skills/ci-review.md from trusted base 168682264c66.
Review mode: full
View review run: https://github.com/ConductorOne/baton-snowflake/actions/runs/32989061987

Review Summary

Scanned the full PR diff for security and correctness: it is a single added //go:generate go run ./gen line in pkg/config/config.go. Verified the directive resolves correctly — go generate runs with the working directory set to pkg/config, so ./gen matches the existing pkg/config/gen/gen.go (package main, calling config.Generate with the snowflake configuration), and the SDK generator writes conf.gen.go relative to that directory, which is exactly the path the Makefile generate target expects. No duplicate directive exists elsewhere in the repo, pkg/config/conf.gen.go is untouched, no dependency manifests changed, and there is no import cycle since gen is a separate main package. No issues found.

Security Issues

None found.

Correctness Issues

None found.

Suggestions

None.

[github-actions]

No blocking issues found.